Triple
T15431373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker 70 |
E369648
|
entity |
| Predicate | fuselageLengthComparedTo |
P118749
|
FINISHED |
| Object | shorter than Fokker 100 |
—
|
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: shorter than Fokker 100 | Statement: [Fokker 70, fuselageLengthComparedTo, shorter than Fokker 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageLengthComparedTo Context triple: [Fokker 70, fuselageLengthComparedTo, shorter than Fokker 100]
-
A.
fuselageLengthRange
Indicates the range of possible or specified lengths of a fuselage, typically expressed as a minimum and maximum value.
-
B.
fuselageLengthComparedTo747-100
Indicates how the length of an aircraft’s fuselage compares to that of a Boeing 747-100.
-
C.
fuselageDiameter
Indicates the diameter measurement of an aircraft’s fuselage in the described context.
-
D.
fuselageType
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
E.
fuselageVariant
Indicates that one fuselage is a specific version or variant derived from another fuselage design.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ed8ea888190bff8dc14859cca31 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.