Triple
T30145191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAN D26 |
E766234
|
entity |
| Predicate | typicalTorqueRange |
P178510
|
FINISHED |
| Object | high-torque output suitable for heavy-duty use |
—
|
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: high-torque output suitable for heavy-duty use | Statement: [MAN D26, typicalTorqueRange, high-torque output suitable for heavy-duty use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTorqueRange Context triple: [MAN D26, typicalTorqueRange, high-torque output suitable for heavy-duty use]
-
A.
torqueRange
chosen
Indicates the range of torque values within which an action, interaction, or mechanical relationship is valid or operates.
-
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.
torque
Indicates a rotational force applied by one entity on another around a pivot or axis.
-
D.
powerRange
Indicates the range of power values within which an entity operates, applies, or is considered valid.
-
E.
maximumTorqueRpm
Indicates the engine speed, in revolutions per minute, at which the maximum torque is produced.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:18 p.m.