Triple
T29563278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudan Airways |
E750094
|
entity |
| Predicate | operatesUnderIATACode |
P87841
|
FINISHED |
| Object | SD |
—
|
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: SD | Statement: [Sudan Airways, operatesUnderIATACode, SD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesUnderIATACode Context triple: [Sudan Airways, operatesUnderIATACode, SD]
-
A.
operatedUnderIATACode
chosen
Indicates that an entity conducts its operations using the specified IATA (International Air Transport Association) code.
-
B.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
C.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
D.
governingBodyOfIATACode
Indicates that one entity serves as the governing or assigning authority responsible for a given IATA code associated with another entity.
-
E.
hasIATAIndustryCode
Indicates that an entity is associated with a specific IATA industry code that classifies its role or function in the air transport industry.
- F. None of above.
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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: April 28, 2026, 5:21 p.m.