Triple
T20938742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha PW50 |
E515656
|
entity |
| Predicate | hasMonoshockRearSuspension |
P11929
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yamaha PW50, hasMonoshockRearSuspension, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonoshockRearSuspension Context triple: [Yamaha PW50, hasMonoshockRearSuspension, true]
-
A.
suspensionRear
Indicates that the relationship or action involves the rear suspension component or system of an object, typically a vehicle.
-
B.
suspensionType
chosen
Indicates the specific kind or configuration of suspension system associated with an entity (e.g., a vehicle or structure).
-
C.
isOnRearPlate
Indicates that one entity is positioned on or attached to the rear plate of another entity.
-
D.
frontShockTowers
Indicates a relationship where front shock towers are present on, attached to, or associated with a vehicle’s front suspension or chassis.
-
E.
hasLeadingWheelArrangement
Indicates the specific configuration of the leading (front) wheels in a vehicle’s or locomotive’s wheel arrangement.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f95419a48190b7f62abc59f38bef |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:50 p.m.