Triple

T1147966
Position Surface form Disambiguated ID Type / Status
Subject Boeing 777 E23610 entity
Predicate ICAOTypeDesignator P16898 FINISHED
Object B772 E23610 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: B772 | Statement: [Boeing 777, ICAOTypeDesignator, B772]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: B772
Context triple: [Boeing 777, ICAOTypeDesignator, B772]
  • A. Boeing 777 chosen
    The Boeing 777 is a long-range, wide-body twin-engine jet airliner widely used by airlines around the world for international passenger flights.
  • B. Boeing 757
    The Boeing 757 is a mid-size, narrow-body twin-engine jet airliner widely used for short- to medium- and some long-haul routes, known for its strong performance and versatility.
  • C. Boeing 720
    The Boeing 720 is a shorter-range, lighter derivative of the Boeing 707 jet airliner, designed primarily for medium-haul routes in the early jet age.
  • D. Boeing 767
    The Boeing 767 is a wide-body, twin-engine jet airliner widely used for medium- to long-haul commercial flights and cargo operations.
  • E. Airbus A321
    The Airbus A321 is a stretched, single-aisle commercial jet airliner widely used for short- to medium-haul passenger flights.
  • 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_69a493f0d32c8190ac74bad3c87f2641 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc7041248190893e4c655dbd0604 completed March 1, 2026, 10:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac76405074819089f001916748b466 completed March 7, 2026, 7:02 p.m.
Created at: March 1, 2026, 7:44 p.m.