Triple
T3965222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 04L/22R |
E92200
|
entity |
| Predicate | hasIATACodeOfAirport |
P2569
|
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: [Runway 04L/22R, hasIATACodeOfAirport, ORD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ORD Context triple: [Runway 04L/22R, hasIATACodeOfAirport, 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.
OR
OR is the official two-letter United States Postal Service abbreviation for the state of Oregon.
-
C.
ORCP
ORCP is the standard legal abbreviation for the Oregon Rules of Civil Procedure, which govern civil court proceedings in the state of Oregon.
-
D.
ORS
ORS is the commonly used abbreviation for the Oregon Revised Statutes, the codified laws governing the U.S. state of Oregon.
-
E.
OAR
OAR is the commonly used abbreviation for the Oregon Administrative Rules, which comprise the codified regulations issued by Oregon’s state agencies.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef97520588190922e56201fc3ca52 |
completed | March 9, 2026, 4:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5400311bc81908379313e2d444557 |
completed | March 14, 2026, 11:01 a.m. |
Created at: March 9, 2026, 3:31 p.m.