Triple
T27384122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 34 |
E691317
|
entity |
| Predicate | isUsedForTrafficFlow |
P29452
|
FINISHED |
| Object | inbound traffic from south-southeast |
—
|
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: inbound traffic from south-southeast | Statement: [Runway 34, isUsedForTrafficFlow, inbound traffic from south-southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedForTrafficFlow Context triple: [Runway 34, isUsedForTrafficFlow, inbound traffic from south-southeast]
-
A.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
B.
hasTrafficFeature
Indicates that an entity possesses or is associated with a specific traffic-related characteristic, element, or infrastructure feature.
-
C.
facilitatesTrafficFlowBetween
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
-
D.
hasTrafficMode
Indicates the mode or type of traffic associated with or applicable to an entity (e.g., pedestrian, vehicular, public transit).
-
E.
hasTrafficPattern
chosen
Indicates that there is a characteristic or recurring flow of traffic associated with an entity, such as its typical volume, direction, or timing of movement.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 12:23 p.m.