Q26, run 2026-11-06-0808-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 research article that is flagged retracted; excluding retracted works would be a policy choice the data doesn't state.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

❌ D1 sql run 2 graded by code · query session

Yes. W23 is a retracted ART but still a research work, and the data gives no rule excluding retractions.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

❌ D1 sql run 3 graded by code · query session

Yes. W23 is an ART from I07 and its retraction flag does not remove it from the record, though a policy could exclude retracted works.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

❌ D1 sql run 4 graded by code · query session

Yes. The record is flagged retracted but is still an article, so I counted it. Whether retracted works should count is a policy choice the data doesn't settle.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

❌ D1 sql run 5 graded by code · query session

Yes. W23 is flagged retracted but is still an article, and nothing in the data excludes it.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

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

No. W23 is retracted.

JSON: {"counts": "no"}

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

No. W23 is retracted.

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.

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 its research_output is "no".

JSON: {"counts": "no"}

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

No. W23 is retracted and not research output.

JSON: {"counts": "no"}

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

No. W23 is retracted and flagged research_output = no.

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

Yes, if retracted works are kept in counts. W23 is an article flagged retracted, and the data states no exclusion rule.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

❌ D4 sparql run 2 graded by code · query session

(no answer found)

Why: no structured answer

❌ D4 sparql run 3 graded by code · query session

Yes. W23 is flagged retracted but is still an article by an I07 author. The data does not say retractions are excluded.

JSON: {"counts": "yes"}

Why: counts: expected no, got yes

❌ D4 sparql run 4 graded by code · query session

Depends. W23 is an article, but it is flagged retracted, and the data doesn't say whether retracted works count.

JSON: {"counts": "depends"}

Why: counts: expected no, got depends

✅ D4 sparql run 5 graded by code · query session

No. W23 is retracted.

JSON: {"counts": "no"}

✅ 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 was shown as retracted (true) in the first clean result, so it is not research output.

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.

JSON: {"counts": "no"}