Triple
T38059559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanwick Oceanic Control Area |
E950301
|
entity |
| Predicate | hasAirspaceClass |
P70676
|
FINISHED |
| Object | Class A 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: Class A airspace | Statement: [Shanwick Oceanic Control Area, hasAirspaceClass, Class A airspace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirspaceClass Context triple: [Shanwick Oceanic Control Area, hasAirspaceClass, Class A airspace]
-
A.
hasAirspace
Indicates that one entity possesses, controls, or is associated with a defined region of airspace relative to another entity or area.
-
B.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
C.
isInAirspaceRegion
Indicates that an entity is located within or passing through a specified airspace region.
-
D.
airspaceType
chosen
Indicates the classification or category of airspace that applies to a given location or flight segment.
-
E.
hasUncontrolledAirspace
Indicates that an entity (such as a location or region) includes or is associated with airspace that is not subject to active air traffic control.
- 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_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. |
Created at: May 3, 2026, 4:21 p.m.