Triple

T2754416
Position Surface form Disambiguated ID Type / Status
Subject Airbus A318 E61065 entity
Predicate ICAOTypeDesignator P16898 FINISHED
Object A318 E61065 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: A318 | Statement: [Airbus A318, ICAOTypeDesignator, A318]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A318
Context triple: [Airbus A318, ICAOTypeDesignator, A318]
  • A. Airbus A318 chosen
    The Airbus A318 is the smallest variant of Airbus's A320-series narrow-body airliners, designed for short- to medium-haul routes with reduced passenger capacity.
  • B. Airbus A319
    The Airbus A319 is a short- to medium-range, narrow-body commercial airliner in the Airbus A320 family, widely used by airlines around the world for passenger services.
  • 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 A330
    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.
  • 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_69ab4b7a85bc819094a349b84beb1f2c completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdb7073d081909da84b21015972f2 completed March 7, 2026, 8:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69afbbdb43d481909bf4e61840979c0a completed March 10, 2026, 6:36 a.m.
Created at: March 6, 2026, 9:56 p.m.