Triple

T17473705
Position Surface form Disambiguated ID Type / Status
Subject Laupheim Air Base E425482 entity
Predicate hasHelicopterUnit P99164 FINISHED
Object special operations helicopter forces 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: special operations helicopter forces | Statement: [Laupheim Air Base, hasHelicopterUnit, special operations helicopter forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHelicopterUnit
Context triple: [Laupheim Air Base, hasHelicopterUnit, special operations helicopter forces]
  • A. isHelicopterOf
    Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
  • B. hasHelicopterTrainingRole
    Indicates that an entity holds a role or position specifically related to the training or instruction of helicopter operations.
  • C. isHelicopterOnly
    Indicates that the subject is restricted to or designated exclusively for use by helicopters.
  • D. hasHelicopterTraffic chosen
    Indicates that there is regular or notable helicopter movement or operations occurring in or over a given area or location.
  • E. hasHeliport
    Indicates that an entity possesses or is equipped with a heliport facility for helicopter landing and takeoff.
  • 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451b990848190b2e8510d67e94b79 completed April 19, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69e3b4f341c88190adabe526d8903b05 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:47 a.m.