Triple

T38059745
Position Surface form Disambiguated ID Type / Status
Subject Shanwick Oceanic FIR E950306 entity
Predicate hasStandardRouteStructure P40317 FINISHED
Object North Atlantic Organized Track System NE NERFINISHED

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: North Atlantic Organized Track System | Statement: [Shanwick Oceanic FIR, hasStandardRouteStructure, North Atlantic Organized Track System]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStandardRouteStructure
Context triple: [Shanwick Oceanic FIR, hasStandardRouteStructure, North Atlantic Organized Track System]
  • A. isStandardRouteOn chosen
    Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
  • B. hasMajorStructureOnRoute
    Indicates that a significant physical structure is located along or directly associated with a particular route.
  • C. hasRoute
    Indicates that there exists a path or connection enabling travel or communication from one entity to another.
  • D. hasFixedRoute
    Indicates that an entity follows a predetermined, unchanging path or sequence of locations when operating or moving.
  • E. hasCommonRoute
    Indicates that two or more entities share at least one overlapping or identical route or path.
  • 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_6a00a74c0564819081e1c4c29b9d0d15 completed May 10, 2026, 3:42 p.m.
PD Predicate disambiguation batch_6a00a6a63ef48190a743c88534d9d672 completed May 10, 2026, 3:39 p.m.
Created at: May 3, 2026, 4:21 p.m.