Triple
T15744398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTAC |
E381683
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Esenboğa |
E1176415
|
NE FINISHED |
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: Esenboğa | Statement: [LTAC, nearCity, Esenboğa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Esenboğa Context triple: [LTAC, nearCity, Esenboğa]
-
A.
Esenboğa
chosen
Esenboğa is a district and locality near Ankara, Turkey, best known for hosting Ankara’s main international airport.
-
B.
Etimesgut
Etimesgut is a rapidly growing suburban district and municipality on the western side of Ankara, Turkey’s capital city.
-
C.
Çankaya
Çankaya is a central district of Ankara, Turkey, known for housing key government institutions, foreign embassies, and major national landmarks.
-
D.
Nişantaşı
Nişantaşı is an upscale neighborhood in Istanbul known for its luxury shopping streets, stylish cafes, and elegant residential buildings.
-
E.
Bağçasaray
Bağçasaray is the Crimean Tatar name for Bakhchisaray, a historic town in Crimea that once served as the capital of the Crimean Khanate.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0502c0c3c8190b8e512df307039c1 |
completed | April 16, 2026, 2:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9981e0d081909617b5d686905d3a |
completed | May 9, 2026, 8:30 p.m. |
Created at: April 10, 2026, 4:46 a.m.