Triple
T1942286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DuPage Airport |
E41581
|
entity |
| Predicate | runwayLighting |
P13444
|
FINISHED |
| Object | high-intensity runway lights |
—
|
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: high-intensity runway lights | Statement: [DuPage Airport, runwayLighting, high-intensity runway lights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayLighting Context triple: [DuPage Airport, runwayLighting, high-intensity runway lights]
-
A.
hasRunwayLighting
chosen
Indicates that a runway is equipped with lighting systems to aid visibility and operations, typically during low-light or night conditions.
-
B.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
-
C.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
D.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
E.
hasRunwayMarkings
Indicates that a runway possesses specific painted markings or symbols on its surface.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.