Triple
T1093587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 787 Dreamliner |
E24221
|
entity |
| Predicate | IATADesignator |
P3732
|
FINISHED |
| Object | 788 (for 787-8) |
—
|
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: 788 (for 787-8) | Statement: [Boeing 787 Dreamliner, IATADesignator, 788 (for 787-8)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IATADesignator Context triple: [Boeing 787 Dreamliner, IATADesignator, 788 (for 787-8)]
-
A.
NATODesignation
Indicates that one entity is the official name or code assigned to another entity by NATO for identification or classification purposes.
-
B.
ICAOTypeDesignator
Indicates the standardized aircraft type code assigned by ICAO that specifies the model or family of an aircraft used in aviation operations and documentation.
-
C.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
E.
designationAuthority
Indicates the entity that has the official power or responsibility to assign, grant, or confer a particular designation to another entity.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99d1e8c81909cf1178d68d38885 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b743175481908f3967e589717c55 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.