Triple
T2773266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-114 |
E61507
|
entity |
| Predicate | icaoDesignator |
P16898
|
FINISHED |
| Object | TU11 |
—
|
LITERAL 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: TU11 | Statement: [Tupolev Tu-114, icaoDesignator, TU11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: icaoDesignator Context triple: [Tupolev Tu-114, icaoDesignator, TU11]
-
A.
ICAOTypeDesignator
chosen
Indicates the standardized aircraft type code assigned by ICAO that specifies the model or family of an aircraft used in aviation operations and documentation.
-
B.
callsignForIATACode
Indicates that a particular airline callsign is associated with a given IATA airline code.
-
C.
AVADesignation
Indicates that an entity has been assigned a specific AVA (American Viticultural Area) designation, linking it to a formally recognized wine-growing region.
-
D.
aircraftDesignationPrefix
Indicates the standardized prefix used in an aircraft’s designation that conveys its type, role, or function.
-
E.
missionDesignationPrefix
Indicates the standardized prefix string used to label or identify a mission within a naming or designation system.
- F. None of above.
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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.