Triple
T4222453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CHI |
E94372
|
entity |
| Predicate | hasIATAOverlap |
P55402
|
FINISHED |
| Object | CHI (Chicago area airport code group) |
—
|
LITERAL 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: CHI (Chicago area airport code group) | Statement: [CHI, hasIATAOverlap, CHI (Chicago area airport code group)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIATAOverlap Context triple: [CHI, hasIATAOverlap, CHI (Chicago area airport code group)]
-
A.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
B.
hasCodeShareOrInterline
Indicates that there exists a codeshare or interline agreement relationship between the referenced transportation services or carriers.
-
C.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
D.
hasInternationalTerminal
Indicates that a transportation facility includes a terminal specifically designated for handling international arrivals and departures.
-
E.
associatedWithIATAAirlineCode
Indicates that an entity is linked to or identified by a specific IATA airline 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e4ace648190acf911853d4fcf86 |
completed | March 12, 2026, 11:37 p.m. |
Created at: March 12, 2026, 11:04 p.m.