Triple
T35890496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosworth DFR engine |
E1037766
|
entity |
| Predicate | maxEngineSpeed |
P98321
|
FINISHED |
| Object | over 11,000 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: over 11,000 rpm | Statement: [Cosworth DFR engine, maxEngineSpeed, over 11,000 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxEngineSpeed Context triple: [Cosworth DFR engine, maxEngineSpeed, over 11,000 rpm]
-
A.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
maximumRPM
chosen
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
C.
maximumContinuousPowerRPM
Indicates the engine speed, in revolutions per minute, at which the system can continuously deliver its maximum allowable power without exceeding operational limits.
-
D.
maximumCurrentSpeed
Indicates the highest current speed value that an entity is allowed or able to reach under present conditions.
-
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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3951e08190ac553bf8b0c2e7bd |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.