Triple
T15755486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian airspace |
E381956
|
entity |
| Predicate | upperAirspaceLimit |
P36360
|
FINISHED |
| Object | flight level 660 (approximate operational) |
—
|
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: flight level 660 (approximate operational) | Statement: [Norwegian airspace, upperAirspaceLimit, flight level 660 (approximate operational)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperAirspaceLimit Context triple: [Norwegian airspace, upperAirspaceLimit, flight level 660 (approximate operational)]
-
A.
upperLimit
chosen
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
B.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
C.
aircraftHeight
Indicates the vertical distance or altitude of an aircraft relative to a reference level (such as ground or sea level).
-
D.
altitudeOfRecordFlight
Indicates the altitude reached during a particular record-setting flight.
-
E.
hasAirspace
Indicates that one entity possesses, controls, or is associated with a defined region of airspace relative to another entity or area.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b1ff4881909d5240d1d30f5c8b |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.