Triple

T22620563
Position Surface form Disambiguated ID Type / Status
Subject CF6-6 E558264 entity
Predicate engineFamily P18926 FINISHED
Object CF6 series NE NERFINISHED

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: CF6 series | Statement: [CF6-6, engineFamily, CF6 series]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CF6 series
Context triple: [CF6-6, engineFamily, CF6 series]
  • A. CF6-6 chosen
    The CF6-6 is an early, lower-thrust member of General Electric’s CF6 high-bypass turbofan engine family, used primarily to power wide-body commercial airliners.
  • B. CF6-50
    The CF6-50 is a widely used, higher-thrust variant of General Electric’s CF6 turbofan engine developed for wide-body commercial airliners in the 1970s.
  • C. CF6-80A
    The CF6-80A is an early, high-bypass turbofan variant in General Electric’s CF6 engine family, developed primarily to power wide-body commercial airliners.
  • D. CF6-80 series
    The CF6-80 series is a family of high-bypass turbofan aircraft engines produced by General Electric and widely used on various commercial wide-body airliners.
  • E. CF6-80C2
    The CF6-80C2 is a widely used high-bypass turbofan engine variant in General Electric’s CF6 family, powering numerous commercial and military wide-body aircraft with improved efficiency and reliability.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24545a8e08190bfa7482a2c725ff1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f16e383b048190a432c540185916d0 completed April 29, 2026, 2:34 a.m.
Created at: April 17, 2026, 3 p.m.