Triple
T17180803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda CBR1100XX |
E416975
|
entity |
| Predicate | claimedTorque |
P5895
|
FINISHED |
| Object | approximately 124 Nm |
—
|
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: approximately 124 Nm | Statement: [Honda CBR1100XX, claimedTorque, approximately 124 Nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedTorque Context triple: [Honda CBR1100XX, claimedTorque, approximately 124 Nm]
-
A.
torque
chosen
Indicates a rotational force applied by one entity on another around a pivot or axis.
-
B.
tractionPower
Indicates the amount of mechanical or electrical power available or used to provide tractive force for movement or propulsion.
-
C.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
D.
improvedTorqueComparedTo
Indicates that one entity provides greater torque performance than another entity used as a reference.
-
E.
maximumTorque
Indicates the greatest amount of torque that can be produced, transmitted, or withstood in the specified 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc1187808190aeaa0d0e6487957e |
completed | April 18, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.