Triple

T21923113
Position Surface form Disambiguated ID Type / Status
Subject Shannon Flight Information Region E541369 entity
Predicate appliesProcedures P15181 FINISHED
Object ICAO oceanic procedures 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: ICAO oceanic procedures | Statement: [Shannon Flight Information Region, appliesProcedures, ICAO oceanic procedures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesProcedures
Context triple: [Shannon Flight Information Region, appliesProcedures, ICAO oceanic procedures]
  • A. overseesProcedure
    Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
  • B. hasSpecialProcedure chosen
    Indicates that a particular entity is associated with or governed by a designated special procedure or process.
  • C. appliesProgram
    Indicates that an agent initiates or carries out a specific program, procedure, or course of action on or for a target entity.
  • D. proceduresVaryBy
    Indicates that the procedures or methods used differ depending on a specified factor, context, or category.
  • E. procedureFeature
    Indicates that a procedure possesses, involves, or is characterized by a particular feature or attribute.
  • 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_69e0c47d74488190a15119108794a307 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1233d096c8190af0d7cd21879c91b completed April 28, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69e6f5efc208819091ed2cf6841fa600 completed April 21, 2026, 3:58 a.m.
Created at: April 16, 2026, 7:45 p.m.