Triple

T28090837
Position Surface form Disambiguated ID Type / Status
Subject San Juan Airport E709948 entity
Predicate hasNavigationServices P146575 FINISHED
Object basic air navigation services 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: basic air navigation services | Statement: [San Juan Airport, hasNavigationServices, basic air navigation services]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNavigationServices
Context triple: [San Juan Airport, hasNavigationServices, basic air navigation services]
  • A. hasNavigationService chosen
    Indicates that an entity provides, supports, or is associated with a navigation-related service or functionality for another entity.
  • B. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • C. hasNavigationCharacteristic
    Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
  • D. hasNavigationTechnology
    Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
  • E. hasNavigationStatus
    Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
  • 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_69ef9b70fd108190a875953b2e50ca91 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69fccdd496048190bca801a8a9eecb62 completed May 7, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69fcccee6240819084680887731ff64b completed May 7, 2026, 5:33 p.m.
Created at: April 27, 2026, 8:58 p.m.