Triple
T38059542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanwick Oceanic Control Area |
E950301
|
entity |
| Predicate | requiresFlightPlanType |
P202699
|
FINISHED |
| Object | oceanic clearance |
—
|
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 clearance | Statement: [Shanwick Oceanic Control Area, requiresFlightPlanType, oceanic clearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresFlightPlanType Context triple: [Shanwick Oceanic Control Area, requiresFlightPlanType, oceanic clearance]
-
A.
requiresForVFR
Indicates that one entity must be present, satisfied, or fulfilled as a prerequisite for another entity to operate or be valid under Visual Flight Rules (VFR).
-
B.
fareRequired
Indicates that a payment or fare is required for access to or use of a service, route, or transportation option.
-
C.
usedInFlightPlansFor
Indicates that something (e.g., data, a procedure, or a resource) is employed as part of creating or executing flight plans for specific flights or routes.
-
D.
aircraftRoleRequired
Indicates that a specific operational role or function is required of an aircraft within a given context or mission.
-
E.
requiresForIFR
Indicates that one entity must be present, satisfied, or fulfilled in order for another entity to be valid or operable under Instrument Flight Rules (IFR).
- 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_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_6a00ada1f3588190a7138e9f9afb9a6b |
completed | May 10, 2026, 4:09 p.m. |
Created at: May 3, 2026, 4:21 p.m.