Triple
T746968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 4 (LAX) |
E15362
|
entity |
| Predicate | hasRunwayAccessVia |
P18604
|
FINISHED |
| Object | LAX airfield |
—
|
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: LAX airfield | Statement: [Terminal 4 (LAX), hasRunwayAccessVia, LAX airfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunwayAccessVia Context triple: [Terminal 4 (LAX), hasRunwayAccessVia, LAX airfield]
-
A.
hasRunwayType
Indicates that an airport or airfield has a runway of a specified type or surface classification.
-
B.
hasRunwayNumber
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
C.
hasRunwayMarkings
Indicates that a runway possesses specific painted markings or symbols on its surface.
-
D.
hasRunwayOrientation
Indicates that a runway is aligned or oriented in a specific directional heading.
-
E.
hasRunwayConfigurationRole
Indicates that an entity plays a specific functional role within a particular runway configuration.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62ca1d081908e3191411f86498d |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a57267c481909790a1fda3fced08 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.