Triple
T8629229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bentley Mulsanne |
E204357
|
entity |
| Predicate | torqueOutputApprox |
P5895
|
FINISHED |
| Object | 752 lb ft |
—
|
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: 752 lb ft | Statement: [Bentley Mulsanne, torqueOutputApprox, 752 lb ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torqueOutputApprox Context triple: [Bentley Mulsanne, torqueOutputApprox, 752 lb ft]
-
A.
torqueDistribution
Indicates how torque or rotational force is apportioned among multiple components, such as wheels, axles, or motors, within a system.
-
B.
torque
chosen
Indicates a rotational force applied by one entity on another around a pivot or axis.
-
C.
powerOutputRpm
Indicates the relationship between a system’s power output and the rotational speed (in revolutions per minute) at which that power is produced.
-
D.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
E.
hasOpenLoopVoltageGainTypical
Indicates that the relationship specifies the typical value of an entity’s open-loop voltage gain in an electrical or electronic context.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.