Triple
T4368016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary/Chicago International Airport |
E98824
|
entity |
| Predicate | hasRunwayExtensionProject |
P55804
|
FINISHED |
| Object | completed in 2010s |
—
|
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: completed in 2010s | Statement: [Gary/Chicago International Airport, hasRunwayExtensionProject, completed in 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunwayExtensionProject Context triple: [Gary/Chicago International Airport, hasRunwayExtensionProject, completed in 2010s]
-
A.
hasRunwayExtension
Indicates that a runway has an additional extended section beyond its original length.
-
B.
runwayExtendedFor
Indicates that a runway has been lengthened or expanded to accommodate or serve a particular aircraft, operation, or purpose.
-
C.
hasRunwaySide
Indicates that a runway is located on or associated with a particular side or boundary of another feature (such as an airport or airfield area).
-
D.
hasRunwayPresence
Indicates that an entity maintains a physical runway or landing strip suitable for aircraft operations.
-
E.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352034d3881909ed4b2f9eef5e823 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:17 p.m.