Triple
T17180801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda CBR1100XX |
E416975
|
entity |
| Predicate | claimedPower |
P16215
|
FINISHED |
| Object | approximately 164 hp at crank |
—
|
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 164 hp at crank | Statement: [Honda CBR1100XX, claimedPower, approximately 164 hp at crank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedPower Context triple: [Honda CBR1100XX, claimedPower, approximately 164 hp at crank]
-
A.
assertedPower
Indicates that one entity has claimed, declared, or exercised authority, control, or dominance over another entity or domain.
-
B.
claimedRight
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
C.
confirmationPower
Indicates that one entity has the authority or capacity to approve, validate, or formally confirm the actions, decisions, or status of another entity.
-
D.
claimed
chosen
Indicates that an entity has asserted or stated something as true, often without definitive proof or verification.
-
E.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
- 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.