Triple

T5955916
Position Surface form Disambiguated ID Type / Status
Subject General Electric CF6 E132513 entity
Predicate application P98 FINISHED
Object Airbus A330 E38704 NE 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: Airbus A330 | Statement: [General Electric CF6, application, Airbus A330]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Airbus A330
Context triple: [General Electric CF6, application, Airbus A330]
  • A. Airbus A330 chosen
    The Airbus A330 is a wide-body, twin-engine jet airliner designed for medium- to long-haul routes and widely used by airlines around the world.
  • B. Airbus A340
    The Airbus A340 is a long-range, four-engine wide-body commercial airliner designed for intercontinental passenger flights.
  • C. Airbus A321
    The Airbus A321 is a stretched, single-aisle commercial jet airliner widely used for short- to medium-haul passenger flights.
  • D. Airbus A300
    The Airbus A300 is a wide-body twin-engine jet airliner introduced in the 1970s as Airbus’s first commercial aircraft and one of the world’s earliest twin-engine wide-bodies.
  • E. Airbus A310
    The Airbus A310 is a twin-engine, wide-body jet airliner introduced in the early 1980s as a shorter, more efficient derivative of the Airbus A300 for medium- to long-haul routes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c0086b05cc8190a8f36a96927a525c completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c039c1de80819085c97a0aa2d37f32 completed March 22, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0e361ad508190928f0ce0f12231c9 completed March 23, 2026, 6:53 a.m.
Created at: March 22, 2026, 4:02 p.m.