Triple

T38059554
Position Surface form Disambiguated ID Type / Status
Subject Shanwick Oceanic Control Area E950301 entity
Predicate usesProceduralControl P193451 FINISHED
Object non-radar separation 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: non-radar separation | Statement: [Shanwick Oceanic Control Area, usesProceduralControl, non-radar separation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesProceduralControl
Context triple: [Shanwick Oceanic Control Area, usesProceduralControl, non-radar separation]
  • A. hasProceduralInstrument
    Indicates that a procedure or process is carried out using, or with the aid of, a specified instrument or tool.
  • B. hasProceduralRole
    Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
  • C. usedToControl
    Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
  • D. requiresControlSystem
    Indicates that one entity depends on or mandates the presence of a control system associated with another entity in order to function or be valid.
  • E. isRemoteControlled
    Indicates that an entity is operated or controlled from a distance via a remote device or system.
  • 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_69fd474b7e788190a9bb9b542d878f60 completed May 8, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69fd46d8b2f0819099d92d72c902f60e completed May 8, 2026, 2:13 a.m.
PDg Predicate description generation batch_69fd474a71648190b6b6ae4991db81b1 completed May 8, 2026, 2:15 a.m.
Created at: May 3, 2026, 4:21 p.m.