Triple
T10786850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5.2L Voodoo V8 |
E254472
|
entity |
| Predicate | maximumHorsepowerRpm |
P56150
|
FINISHED |
| Object | 7500 rpm |
—
|
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: 7500 rpm | Statement: [5.2L Voodoo V8, maximumHorsepowerRpm, 7500 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumHorsepowerRpm Context triple: [5.2L Voodoo V8, maximumHorsepowerRpm, 7500 rpm]
-
A.
horsepower
Indicates the power output or performance capacity associated with an entity, typically measuring how much work it can perform over time.
-
B.
maximumTorque
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified context.
-
C.
powerOutputRpm
chosen
Indicates the relationship between a system’s power output and the rotational speed (in revolutions per minute) at which that power is produced.
-
D.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d5422481908d7ab833c6cbc879 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.