Triple

T38059531
Position Surface form Disambiguated ID Type / Status
Subject Shanwick Oceanic Control Area E950301 entity
Predicate usesSeparationStandard P90529 FINISHED
Object reduced longitudinal 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: reduced longitudinal separation | Statement: [Shanwick Oceanic Control Area, usesSeparationStandard, reduced longitudinal separation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesSeparationStandard
Context triple: [Shanwick Oceanic Control Area, usesSeparationStandard, reduced longitudinal separation]
  • A. recognizedAsSeparateStandardBy
    Indicates that something is acknowledged or treated as an independent, distinct standard by a particular authority or group.
  • B. typeOfSeparation chosen
    Indicates the specific manner or category of separation that exists or occurred between entities.
  • C. definedSeparationFrom
    Indicates a formally specified distinction or boundary established between one entity and another.
  • D. usedToSeparate
    Indicates that one entity serves as a means or tool to divide, isolate, or keep other entities apart from each other.
  • E. providesSeparationFor
    Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
  • 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_69fde5d7d9548190880a9d95b8f0f66b completed May 8, 2026, 1:32 p.m.
PD Predicate disambiguation batch_69fde4e1bf9c81909754545275eccc03 completed May 8, 2026, 1:28 p.m.
Created at: May 3, 2026, 4:21 p.m.