Triple

T21089244
Position Surface form Disambiguated ID Type / Status
Subject Aermacchi M-346 Master E519587 entity
Predicate hasVariant P455 FINISHED
Object T-346A 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: T-346A | Statement: [Aermacchi M-346 Master, hasVariant, T-346A]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: T-346A
Context triple: [Aermacchi M-346 Master, hasVariant, T-346A]
  • A. T-346A chosen
    T-346A is the Italian Air Force’s designation for the M-346 Master, an advanced jet trainer and light attack aircraft developed by Leonardo.
  • B. T-34A
    The T-34A is the initial production version of the Beechcraft T-34 Mentor, used primarily as a basic piston-engine military trainer aircraft.
  • C. TR-36
    TR-36 is the ISO 3166-2 subdivision code assigned to Turkey’s Kars Province.
  • D. T-68
    The T-68 was an early generation light rail tram used on the Manchester Metrolink system in the UK before being superseded by newer models.
  • E. T.38
    T.38 is an ITU-T recommendation that defines a protocol for real-time fax transmission over IP networks.
  • 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_69e0b507dd9081908fb8bfcbef4c8b46 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7094dd65481909391ed74115afc23 completed April 21, 2026, 5:21 a.m.
Created at: April 16, 2026, 2:50 p.m.