Triple

T14542481
Position Surface form Disambiguated ID Type / Status
Subject US-2 E341203 entity
Predicate hasBoundaryLayerControlSystem P114860 FINISHED
Object true 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: true | Statement: [US-2, hasBoundaryLayerControlSystem, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBoundaryLayerControlSystem
Context triple: [US-2, hasBoundaryLayerControlSystem, true]
  • A. hasBoundarySystem
    Indicates that one entity possesses or is associated with a specific boundary system that defines its limits or separation from its surroundings.
  • B. requiresControlSystem
    Indicates that one entity depends on or mandates the presence of a control system associated with another entity in order to function or be valid.
  • C. hasControlledAirspace
    Indicates that a specified location or region falls within airspace where aircraft operations are regulated and managed by an aviation authority.
  • D. hasEnvironmentalControl
    Indicates that one entity regulates, influences, or manages the environmental conditions affecting another entity or area.
  • E. hasOwnBorderControls
    Indicates that an entity independently manages and enforces its own border control policies and procedures, separate from those of other entities.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb1be5a8081909bf727e28a5bba4a completed April 14, 2026, 9:29 p.m.
PD Predicate disambiguation batch_69de5c546c7081909e27d504ec360c5c completed April 14, 2026, 3:25 p.m.
PDg Predicate description generation batch_69de610330a48190b558235a14c0dc9f completed April 14, 2026, 3:45 p.m.
Created at: April 10, 2026, 1:22 a.m.