Triple
T3851720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bursa Yenişehir Airport |
E85308
|
entity |
| Predicate | operatedBy |
P86
|
FINISHED |
| Object | DHMİ |
E381685
|
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: DHMİ | Statement: [Bursa Yenişehir Airport, operatedBy, DHMİ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DHMİ Context triple: [Bursa Yenişehir Airport, operatedBy, DHMİ]
-
A.
DHMİ
chosen
DHMİ is Turkey’s state-owned General Directorate of State Airports Authority, responsible for operating and managing the country’s major airports and air navigation services.
-
B.
Dimlî
Dimlî is a Northwestern Iranian language spoken primarily in eastern Turkey, often considered a major dialect or variety of Zazaki.
-
C.
Dawadmi
Dawadmi is a town in central Saudi Arabia known as an important administrative and commercial center within Riyadh Province.
-
D.
DH
DH is the commonly used currency symbol representing the Moroccan dirham.
-
E.
DH
DH is the postcode area covering Durham and surrounding parts of North East England in the United Kingdom.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebd0feb081909cc1d5bf41e4acd6 |
completed | March 9, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b50419e7a0819087f9bc7fbfec4116 |
completed | March 14, 2026, 6:45 a.m. |
Created at: March 9, 2026, 3:19 p.m.