Triple
T18711225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanmon Kaikyo |
E457518
|
entity |
| Predicate | trafficSeparationScheme |
P16100
|
FINISHED |
| Object | implemented |
—
|
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: implemented | Statement: [Kanmon Kaikyo, trafficSeparationScheme, implemented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficSeparationScheme Context triple: [Kanmon Kaikyo, trafficSeparationScheme, implemented]
-
A.
trafficSeparation
chosen
Indicates a relationship where movement or flow is organized into distinct, non-overlapping paths or zones to prevent interference or collisions.
-
B.
hasTrafficSeparationProvidedBy
Indicates that traffic flow or movement is regulated or organized by a specified traffic separation system or measure.
-
C.
airspaceType
Indicates the classification or category of airspace that applies to a given location or flight segment.
-
D.
providesATCSeparation
Indicates that one entity delivers air traffic control separation services to another, ensuring safe spacing and conflict avoidance between aircraft.
-
E.
airTraffic
Indicates the movement and flow of aircraft through airspace, including their routes, density, and interactions while in flight.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671b34508190b6180f7d6ad50a58 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.