Triple

T6443047
Position Surface form Disambiguated ID Type / Status
Subject San Antonio de los Baños Airfield E138270 entity
Predicate airspaceType P70676 FINISHED
Object controlled military airspace 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: controlled military airspace | Statement: [San Antonio de los Baños Airfield, airspaceType, controlled military airspace]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: airspaceType
Context triple: [San Antonio de los Baños Airfield, airspaceType, controlled military airspace]
  • A. airspaceRole
    Indicates the specific function or responsibility an entity has within a defined airspace.
  • B. appliesToAirspaceOf
    Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
  • C. hasAirspace
    Indicates that one entity possesses, controls, or is associated with a defined region of airspace relative to another entity or area.
  • D. flightRegime
    Indicates the operational conditions or phase of flight under which an aircraft or aerospace vehicle is functioning (e.g., speed, altitude, and atmospheric regime).
  • E. hasAirfieldType
    Indicates that an airfield is classified as having a particular type or category of airfield.
  • 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_69c008aa61ac8190bc96715ed79fe2d8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0698b030481908b7bb4e16a8b3339 completed March 22, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69c060faaf248190bbdc8ff909c8777a completed March 22, 2026, 9:36 p.m.
PDg Predicate description generation batch_69c0623e3cd48190929b0e3cba013909 completed March 22, 2026, 9:42 p.m.
Created at: March 22, 2026, 4:46 p.m.