Triple
T30791768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737-300 |
E784116
|
entity |
| Predicate | fuselageCrossSection |
P156197
|
FINISHED |
| Object | Boeing 737 standard narrow-body |
—
|
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: Boeing 737 standard narrow-body | Statement: [Boeing 737-300, fuselageCrossSection, Boeing 737 standard narrow-body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageCrossSection Context triple: [Boeing 737-300, fuselageCrossSection, Boeing 737 standard narrow-body]
-
A.
fuselageShape
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
-
B.
fuselageDiameter
Indicates the diameter measurement of an aircraft’s fuselage in the described context.
-
C.
fuselageLength_m
Indicates the measured length of an aircraft’s fuselage, expressed in meters.
-
D.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
E.
fuselageDesignBasisFor
chosen
Indicates that a particular fuselage design serves as the foundational basis or reference model for another design, configuration, or derived element.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6900dbd908190baf39dd5cf37d619 |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:42 p.m.