Triple
T38059728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanwick Oceanic FIR |
E950306
|
entity |
| Predicate | trafficEnvironment |
P189922
|
FINISHED |
| Object | Oceanic non-radar airspace |
—
|
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: Oceanic non-radar airspace | Statement: [Shanwick Oceanic FIR, trafficEnvironment, Oceanic non-radar airspace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficEnvironment Context triple: [Shanwick Oceanic FIR, trafficEnvironment, Oceanic non-radar airspace]
-
A.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
B.
roadEnvironment
Indicates that the relationship or action occurs within, is influenced by, or is specifically associated with a road or roadway environment.
-
C.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
D.
trafficLevel
Indicates the degree of congestion or flow intensity present in a transportation network or route at a given time.
-
E.
commercialTrafficStatus
Indicates the current operational condition or level of activity of commercial traffic (e.g., open, restricted, or closed).
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:21 p.m.