Triple

T21923137
Position Surface form Disambiguated ID Type / Status
Subject Dublin Flight Information Region E541370 entity
Predicate hasNavigationService P146575 FINISHED
Object Radar surveillance 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: Radar surveillance | Statement: [Dublin Flight Information Region, hasNavigationService, Radar surveillance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNavigationService
Context triple: [Dublin Flight Information Region, hasNavigationService, Radar surveillance]
  • A. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • B. hasNavigationStatus
    Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
  • C. hasNavigationCharacteristic
    Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
  • D. hasNavigationControl
    Indicates that one entity possesses authority or capability to direct, manage, or influence the movement or course of another entity.
  • E. hasNavigationRoute
    Indicates that one entity provides or defines a navigation path or route leading to or through another entity.
  • 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_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.
PDg Predicate description generation batch_69e6fb6991948190a428c3c3bfd1c3b8 completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 7:45 p.m.