Triple

T4226937
Position Surface form Disambiguated ID Type / Status
Subject Panavia Tornado E94480 entity
Predicate Tornado ECR P55432 FINISHED
Object electronic combat/reconnaissance variant — 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: electronic combat/reconnaissance variant | Statement: [Panavia Tornado, Tornado ECR, electronic combat/reconnaissance variant]
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: Tornado ECR
Context triple: [Panavia Tornado, Tornado ECR, electronic combat/reconnaissance variant]
  • A. eraCode
    Indicates the specific historical or temporal era associated with an entity, typically encoded as a standardized era identifier.
  • B. eraSystem
    Indicates a temporal classification relationship where an entity is associated with a particular era or chronological system used to organize time.
  • C. turret
    Indicates that an entity is equipped with or associated with a turret, typically a rotating weapon or defense mechanism.
  • D. terminusNorth
    Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
  • E. NOC
    Indicates a relationship where one entity is not permitted, not compatible, or otherwise not allowed to occur or coexist with another entity.
  • 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_69b3453700a08190ae88792e3dc63207 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34e5003008190834726e46df3ee9b completed March 12, 2026, 11:37 p.m.
PD Predicate disambiguation batch_69b347f1d7b48190bd8974c03c7dc937 completed March 12, 2026, 11:10 p.m.
PDg Predicate description generation batch_69b34e4ace648190acf911853d4fcf86 completed March 12, 2026, 11:37 p.m.
Created at: March 12, 2026, 11:04 p.m.