Triple
T16266415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moto3 |
E394886
|
entity |
| Predicate | maximumEngineSpeed |
P98321
|
FINISHED |
| Object | 13,500 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: 13,500 rpm | Statement: [Moto3, maximumEngineSpeed, 13,500 rpm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumEngineSpeed Context triple: [Moto3, maximumEngineSpeed, 13,500 rpm]
-
A.
maximumRPM
chosen
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
maximumTorqueRpm
Indicates the engine speed, in revolutions per minute, at which the maximum torque is produced.
-
D.
maximumTorque
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified context.
-
E.
maximumWaterSpeed_kmh
Indicates the highest speed, measured in kilometers per hour, at which an entity can move through water.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.