Triple
T2789968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-22 |
E61904
|
entity |
| Predicate | fuselageLayout |
P21223
|
FINISHED |
| Object | narrow fuselage with rear-mounted engines |
—
|
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: narrow fuselage with rear-mounted engines | Statement: [Tupolev Tu-22, fuselageLayout, narrow fuselage with rear-mounted engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageLayout Context triple: [Tupolev Tu-22, fuselageLayout, narrow fuselage with rear-mounted engines]
-
A.
fuselageShape
chosen
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
-
B.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
C.
fuselageDiameter
Indicates the diameter measurement of an aircraft’s fuselage in the described context.
-
D.
propulsionLayout
Indicates how propulsion components are arranged or configured relative to each other within a system.
-
E.
airframeConstruction
Indicates the method or structural approach used to build an aircraft’s main body and supporting framework.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.