Triple
T17290811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 1 (O'Hare) |
E419778
|
entity |
| Predicate | airportCode |
P418
|
FINISHED |
| Object | ORD |
E89046
|
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: ORD | Statement: [Terminal 1 (O'Hare), airportCode, ORD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ORD Context triple: [Terminal 1 (O'Hare), airportCode, ORD]
-
A.
ORD
chosen
ORD is the three-letter IATA airport code for Chicago O'Hare International Airport, one of the busiest air travel hubs in the United States.
-
B.
Ord
Ord is a surname most notably associated with Boris Ord, the influential 20th-century English organist and choral conductor at King's College, Cambridge.
-
C.
OR
OR is the official two-letter United States Postal Service abbreviation for the state of Oregon.
-
D.
OR
OR is the IATA airline designator assigned to the Dutch leisure carrier Arkefly (now operating as TUI fly Netherlands).
-
E.
OR
OR is the commonly used abbreviation for the Swiss Code of Obligations, the core Swiss federal statute governing contract, company, and commercial law.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e437837d048190949b947f5437636d |
completed | April 19, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a017959ffb0819099d70ed1541158ee |
completed | May 11, 2026, 6:38 a.m. |
Created at: April 10, 2026, 5:40 a.m.