Triple

T6695497
Position Surface form Disambiguated ID Type / Status
Subject Jagdgeschwader 7 "Nowotny" E152737 entity
Predicate unitSpecialization P71511 FINISHED
Object jet fighter operations 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: jet fighter operations | Statement: [Jagdgeschwader 7 "Nowotny", unitSpecialization, jet fighter operations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: unitSpecialization
Context triple: [Jagdgeschwader 7 "Nowotny", unitSpecialization, jet fighter operations]
  • A. hasSpecialUnit
    Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
  • B. specialForcesInvolved
    Indicates that special forces units participate in or are involved in the referenced action, event, or operation.
  • C. uniformSpecialty
    Indicates that multiple entities share the same specific specialty, expertise, or area of focus.
  • D. isEliteUnit
    Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
  • E. imperialAssaultUnits
    Indicates a relationship where certain military units are designated as specialized forces used to carry out assaults on behalf of an empire or imperial 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_69c6880687b08190805278b504d1c92c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6b5ed99e48190970805225458ce82 completed March 27, 2026, 4:53 p.m.
PD Predicate disambiguation batch_69c6ad0e1d348190af1762ea1951038e completed March 27, 2026, 4:15 p.m.
PDg Predicate description generation batch_69c6b5ec6f248190b4fa15fd56dcc01a completed March 27, 2026, 4:53 p.m.
Created at: March 27, 2026, 2:05 p.m.