Triple
T34505758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voodoo |
E885880
|
entity |
| Predicate | maximumPowerOutputRpm |
P171425
|
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: [Voodoo, maximumPowerOutputRpm, 7500 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumPowerOutputRpm Context triple: [Voodoo, maximumPowerOutputRpm, 7500 rpm]
-
A.
maximumRPM
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
B.
maximumContinuousPowerRPM
chosen
Indicates the engine speed, in revolutions per minute, at which the system can continuously deliver its maximum allowable power without exceeding operational limits.
-
C.
maximumTorqueRpm
Indicates the engine speed, in revolutions per minute, at which the maximum torque is produced.
-
D.
powerOutputRpm
Indicates the relationship between a system’s power output and the rotational speed (in revolutions per minute) at which that power is produced.
-
E.
maximumTurboPower
Indicates the highest level of turbo power that can be achieved or utilized in the given 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 2:01 a.m.