Triple
T21970308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3.0-litre Busso V6 |
E542568
|
entity |
| Predicate | torqueCharacteristics |
P146740
|
FINISHED |
| Object | strong low- and mid-range torque |
—
|
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: strong low- and mid-range torque | Statement: [3.0-litre Busso V6, torqueCharacteristics, strong low- and mid-range torque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torqueCharacteristics Context triple: [3.0-litre Busso V6, torqueCharacteristics, strong low- and mid-range torque]
-
A.
torque
Indicates a rotational force applied by one entity on another around a pivot or axis.
-
B.
torqueDistribution
Indicates how torque or rotational force is apportioned among multiple components, such as wheels, axles, or motors, within a system.
-
C.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
D.
maximumTorqueRpm
Indicates the engine speed, in revolutions per minute, at which the maximum torque is produced.
-
E.
maximumTorque
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified context.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1245e4ebc8190968108cc95a22fe4 |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb9b75308190addc3dba7b5d5ddd |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 8:02 p.m.