Triple

T31485708
Position Surface form Disambiguated ID Type / Status
Subject Philippines–United States border E803269 entity
Predicate separatesAirspaceOf P172865 FINISHED
Object Philippines 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: Philippines | Statement: [Philippines–United States border, separatesAirspaceOf, Philippines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: separatesAirspaceOf
Context triple: [Philippines–United States border, separatesAirspaceOf, Philippines]
  • A. appliesToAirspaceOf
    Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
  • B. airspaceType
    Indicates the classification or category of airspace that applies to a given location or flight segment.
  • C. hasAirspace
    Indicates that one entity possesses, controls, or is associated with a defined region of airspace relative to another entity or area.
  • D. trafficSeparation
    Indicates a relationship where movement or flow is organized into distinct, non-overlapping paths or zones to prevent interference or collisions.
  • E. hasControlledAirspace
    Indicates that a specified location or region falls within airspace where aircraft operations are regulated and managed by an aviation authority.
  • 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_69f348ca04508190ba9379b5329dfd75 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6b0d21dd08190a9883ff71c94c71c completed May 3, 2026, 2:20 a.m.
PD Predicate disambiguation batch_69f6aca3dedc81908b519d53d2909868 completed May 3, 2026, 2:02 a.m.
PDg Predicate description generation batch_69f6afeaaef88190aefa97e83f8db906 completed May 3, 2026, 2:16 a.m.
Created at: April 30, 2026, 9:35 p.m.