Triple
T38124038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shosseynaya Airport |
E952017
|
entity |
| Predicate | IATACodeAfterRenaming |
P190034
|
FINISHED |
| Object | LED |
—
|
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: LED | Statement: [Shosseynaya Airport, IATACodeAfterRenaming, LED]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IATACodeAfterRenaming Context triple: [Shosseynaya Airport, IATACodeAfterRenaming, LED]
-
A.
previousICAOcode
Indicates that one entity was the former ICAO (International Civil Aviation Organization) code previously assigned to the other entity.
-
B.
wasRenamedIn
Indicates that an entity changed its name to a different one at or during a specific time or event.
-
C.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
D.
relocatedAndRenamed
Indicates that an entity has moved from one location to another and changed its name as part of that move.
-
E.
usesIATACodeAtOtherEnd
Indicates that one entity identifies or refers to the other end of a route, connection, or relationship using its IATA airport code.
- F. None of above. chosen
Provenance (4 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:21 p.m.