Triple
T20853766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danishmend Emirate |
E513426
|
entity |
| Predicate | notableRuler |
P22
|
FINISHED |
| Object | Yağıbasan |
—
|
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: Yağıbasan | Statement: [Danishmend Emirate, notableRuler, Yağıbasan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yağıbasan Context triple: [Danishmend Emirate, notableRuler, Yağıbasan]
-
A.
Yağıbasan
chosen
Yağıbasan was a prominent 12th-century ruler of the Danishmendid dynasty in Anatolia, known for his political influence and patronage of architecture and learning.
-
B.
Yassıada
Yassıada is one of Istanbul’s Princes' Islands in the Sea of Marmara, historically known for its use as a place of exile and for hosting the 1960–61 trials of Turkish political leaders.
-
C.
Gürsu
Gürsu is a district and rapidly developing urban area located within Turkey’s northwestern Bursa Province.
-
D.
Yakapınar
Yakapınar is a modern settlement in southern Turkey located near the site of the ancient city of Mopsuestia.
-
E.
Keban
Keban is a town in eastern Turkey located near the Euphrates River, known primarily for its proximity to the large hydroelectric Keban Dam.
- 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.