Triple
T20853790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yağıbasan |
E513427
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Niksar |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Niksar | Statement: [Yağıbasan, region, Niksar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Niksar Context triple: [Yağıbasan, region, Niksar]
-
A.
Niksar
chosen
Niksar is a town in modern-day Turkey, historically significant as the site of the ancient city of Neocaesarea in the region of Pontus.
-
B.
Boğazköy
Boğazköy is an important archaeological site in central Turkey best known as the location of Hattusa, the former capital of the Hittite Empire.
-
C.
Kemerburgaz
Kemerburgaz is a neighborhood and semi-rural residential area on the European side of Istanbul, known for its green surroundings and proximity to the Belgrad Forest.
-
D.
Karkamış
Karkamış is a town in southeastern Turkey situated on the Euphrates River, known for its strategic location opposite the Syrian city of Jarabulus and near the ancient archaeological site of Carchemish.
-
E.
Toprakkale
Toprakkale is an ancient fortress and archaeological site in eastern Turkey that served as a significant center of the Iron Age Kingdom of Urartu.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a6015081909f604a88d04b36ea |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 12:44 p.m.