Triple
T18700143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers Jumo diesel engines |
E457225
|
entity |
| Predicate | pistonConfiguration |
P132348
|
FINISHED |
| Object | opposed-piston |
—
|
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: opposed-piston | Statement: [Junkers Jumo diesel engines, pistonConfiguration, opposed-piston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pistonConfiguration Context triple: [Junkers Jumo diesel engines, pistonConfiguration, opposed-piston]
-
A.
pistonStroke
Indicates the distance or movement range that a piston travels within a cylinder during one complete stroke.
-
B.
camshaftConfiguration
Indicates how the camshafts are arranged or configured within an engine’s valve train system.
-
C.
pumpConfiguration
Indicates the specific setup or arrangement in which a pump operates or is installed, including its components, settings, and connections.
-
D.
valvesPerCylinder
Indicates the number of valves associated with each individual cylinder in an engine.
-
E.
boreStrokeDesign
Indicates that an engine’s bore and stroke configuration is designed or specified in a particular way.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562eb06b481908ef9efdb976008f3 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.