Q26, run 2026-11-06-0519-sonnet-query

← back to the run

Does W23 count towards Kesting University's research output?

Tests: Retractions: a retracted work is not research output.

Expected: counts = no

❌ D1 sql run 1 graded by code · query session

Yes. W23 is a retracted article, but it is still an article by I07 and nothing in the data excludes retracted works.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

✅ D1 sql run 2 graded by code · query session

No. W23 is retracted, so it does not count as research output.

JSON: {"counts": "no"}

❌ D1 sql run 3 graded by code · query session

Yes. W23 is an article credited to I07. Retraction is flagged in the data, but nothing in it says retracted works are excluded.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

✅ D1 sql run 4 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

❌ D1 sql run 5 graded by code · query session

Yes. W23 is an ART from I07, and its retraction does not change its type. This depends on whether retracted works are excluded, which the data doesn't say.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

✅ D2 sql+markdown run 1 graded by code · query session

No. W23 is retracted, so it is not research output.

JSON: {"counts": "no"}

✅ D2 sql+markdown run 2 graded by code · query session

No. W23 is retracted, so it is not research output.

JSON: {"counts": "no"}

✅ D2 sql+markdown run 3 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ D2 sql+markdown run 4 graded by code · query session

No. W23 is retracted, so it is not research output.

JSON: {"counts": "no"}

✅ D2 sql+markdown run 5 graded by code · query session

No. W23 is retracted, so it is not research output.

JSON: {"counts": "no"}

✅ D3 sql+executed run 1 graded by code · query session

No. W23 is retracted and not research output.

JSON: {"counts": "no"}

✅ D3 sql+executed run 2 graded by code · query session

No. W23 is retracted and not research output.

JSON: {"counts": "no"}

✅ D3 sql+executed run 3 graded by code · query session

No. W23 is retracted, so it is not research output.

JSON: {"counts": "no"}

✅ D3 sql+executed run 4 graded by code · query session

No. W23 is retracted and not research output.

JSON: {"counts": "no"}

✅ D3 sql+executed run 5 graded by code · query session

No. W23 is retracted and is not research output.

JSON: {"counts": "no"}

✅ D4 sparql run 1 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ D4 sparql run 2 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ D4 sparql run 3 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ D4 sparql run 4 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

❌ D4 sparql run 5 graded by code · query session

Depends. W23 is by A09 at Kesting University, but I did not retrieve its type or retraction status.
**Q27–Q36.** Unresolved.

JSON: {"counts": "depends"}

Why: counts: expected no, got depends

✅ D5 sparql+ontology run 1 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ D5 sparql+ontology run 2 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ D5 sparql+ontology run 3 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ D5 sparql+ontology run 4 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ D5 sparql+ontology run 5 graded by code · query session

No. W23 is retracted, so it is not research output.

JSON: {"counts": "no"}