Triple
T4835131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 11R/29L |
E108039
|
entity |
| Predicate | hasHighTrafficVolume |
P54842
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Runway 11R/29L, hasHighTrafficVolume, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighTrafficVolume Context triple: [Runway 11R/29L, hasHighTrafficVolume, true]
-
A.
hasHeavyTraffic
chosen
Indicates that a location, route, or area is experiencing a high volume of traffic, causing congestion or delays.
-
B.
hasHeavyPassengerTraffic
Indicates that an entity experiences a high volume of passenger movement or usage over a given period.
-
C.
handlesSignificantShareOfTrafficAt
Indicates that an entity is responsible for managing or processing a substantial proportion of the traffic volume at a specified location or system.
-
D.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
E.
hasTrafficPattern
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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.