Triple
T5644711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tacoma Narrows Airport |
E124355
|
entity |
| Predicate | runway 17/35 lighting |
P13444
|
FINISHED |
| Object | runway edge lighting |
—
|
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: runway edge lighting | Statement: [Tacoma Narrows Airport, runway 17/35 lighting, runway edge lighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway 17/35 lighting Context triple: [Tacoma Narrows Airport, runway 17/35 lighting, runway edge lighting]
-
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.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
C.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
-
D.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
E.
runwayWidth
Indicates the measured width of a runway as a spatial dimension.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a8eccc8190837d4705670dc25e |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.