Triple
T17373714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Hare runway system |
E422379
|
entity |
| Predicate | previousConfigurationType |
P51587
|
FINISHED |
| Object | intersecting runway layout |
—
|
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: intersecting runway layout | Statement: [O'Hare runway system, previousConfigurationType, intersecting runway layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousConfigurationType Context triple: [O'Hare runway system, previousConfigurationType, intersecting runway layout]
-
A.
previousConfigurationLocation
Indicates the location where an entity’s earlier or prior configuration was stored or situated.
-
B.
formerlyConfiguration
chosen
Indicates that one entity was previously configured or arranged in the state or setup represented by the other entity, but is no longer so.
-
C.
previousMode
Indicates that one mode directly precedes another in a sequence or state transition.
-
D.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
E.
previousSettlementType
Indicates the type or classification of a settlement that existed at a location before the current or present settlement type.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6b71148190bb10e1fac400d6c3 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.