Triple
T23075306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulzer 12LDA28C |
E575310
|
entity |
| Predicate | pistonStrokeCycle |
P150855
|
FINISHED |
| Object | compression-ignition |
—
|
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: compression-ignition | Statement: [Sulzer 12LDA28C, pistonStrokeCycle, compression-ignition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pistonStrokeCycle Context triple: [Sulzer 12LDA28C, pistonStrokeCycle, compression-ignition]
-
A.
pistonStroke
Indicates the distance or movement range that a piston travels within a cylinder during one complete stroke.
-
B.
numberOfStrokesPerCycle
Indicates the count of individual strokes that occur during one complete cycle of a repeated action or process.
-
C.
engineStrokeType
Indicates the specific stroke-cycle configuration (e.g., two-stroke, four-stroke) that characterizes how an engine completes its power cycle.
-
D.
pistonConfiguration
Indicates the specific arrangement and layout of pistons within an engine or mechanical system.
-
E.
pistons
Indicates a mechanical relationship where pistons convert pressure (often from combustion or fluid) into linear motion or vice versa within an engine or similar system.
- 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c62c200819099c92654493288ad |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:56 p.m.