Triple
T23479589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 737-900ER |
E570366
|
entity |
| Predicate | fuselageLength_m |
P152537
|
FINISHED |
| Object | 42.1 |
—
|
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: 42.1 | Statement: [Boeing 737-900ER, fuselageLength_m, 42.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageLength_m Context triple: [Boeing 737-900ER, fuselageLength_m, 42.1]
-
A.
fuselageLengthComparedTo
Indicates how the length of one fuselage compares to the length of another fuselage, typically in terms of being longer, shorter, or equal.
-
B.
fuselageDiameter
Indicates the diameter measurement of an aircraft’s fuselage in the described context.
-
C.
fuselageLengthRange
Indicates the range of possible or specified lengths of a fuselage, typically expressed as a minimum and maximum value.
-
D.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
E.
fuselageShape
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74f48d8819080e875aaea8b46b3 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:02 p.m.