Triple
T13012680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers J 1 |
E322459
|
entity |
| Predicate | fuselageStructure |
P11768
|
FINISHED |
| Object | monocoque-like structure |
—
|
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: monocoque-like structure | Statement: [Junkers J 1, fuselageStructure, monocoque-like structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuselageStructure Context triple: [Junkers J 1, fuselageStructure, monocoque-like structure]
-
A.
fuselageType
chosen
Indicates the specific structural or design category of an aircraft’s fuselage that an entity belongs to or uses.
-
B.
fuselageShape
Indicates the geometric form or contour of an object's fuselage, describing how its main body is shaped.
-
C.
fuselageVariant
Indicates that one fuselage is a specific version or variant derived from another fuselage design.
-
D.
fuselageCount
Indicates the number of fuselages associated with or contained in an aircraft or aerospace structure.
-
E.
fuselagePosition
Indicates the spatial placement or alignment of a fuselage relative to a reference frame or other aircraft components.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecbb8f4819094d55eb07cb5ad97 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:49 p.m.