Triple
T34194370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz OM642 |
E877197
|
entity |
| Predicate | torqueRange |
P178510
|
FINISHED |
| Object | approximately 440–620 Nm |
—
|
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: approximately 440–620 Nm | Statement: [Mercedes-Benz OM642, torqueRange, approximately 440–620 Nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torqueRange Context triple: [Mercedes-Benz OM642, torqueRange, approximately 440–620 Nm]
-
A.
torque
Indicates a rotational force applied by one entity on another around a pivot or axis.
-
B.
torqueCharacteristics
Indicates the relationship between an object and the specific way its torque behaves or varies under different conditions (e.g., speed, load, or operating state).
-
C.
torqueDistribution
Indicates how torque or rotational force is apportioned among multiple components, such as wheels, axles, or motors, within a system.
-
D.
tuningRange
Indicates the range of values over which something can be tuned or adjusted.
-
E.
maximumTorqueRpm
Indicates the engine speed, in revolutions per minute, at which the maximum torque is produced.
- 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:55 a.m.