Triple
T6018214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737 MAX 10 |
E133998
|
entity |
| Predicate | fuselageStretchComparedToMAX9 |
P68791
|
FINISHED |
| Object | about 66 inches |
—
|
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: about 66 inches | Statement: [Boeing 737 MAX 10, fuselageStretchComparedToMAX9, about 66 inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageStretchComparedToMAX9 Context triple: [Boeing 737 MAX 10, fuselageStretchComparedToMAX9, about 66 inches]
-
A.
fuselageStretchRelativeToMAX8
Indicates the amount by which an aircraft’s fuselage length is increased or decreased relative to the 737 MAX 8 configuration.
-
B.
fuselageLengthComparedTo747-100
Indicates how the length of an aircraft’s fuselage compares to that of a Boeing 747-100.
-
C.
fuselageShape
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
-
D.
fuselageDiameter
Indicates the diameter measurement of an aircraft’s fuselage in the described context.
-
E.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
- F. None of above. chosen
Provenance (4 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f8589d0819089ae7840461640f6 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:07 p.m.