Triple
T20938745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha PW50 |
E515656
|
entity |
| Predicate | hasEnclosedShaftDrive |
P68759
|
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, hasEnclosedShaftDrive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnclosedShaftDrive Context triple: [Yamaha PW50, hasEnclosedShaftDrive, true]
-
A.
hasPrimaryAccessShaft
Indicates that one entity serves as the main access shaft associated with another entity.
-
B.
drivetrainFeature
chosen
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
-
C.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
D.
typicalShaftType
Indicates the usual or characteristic type of shaft associated with an entity or configuration.
-
E.
propulsionShafts
Indicates a relationship where shafts are used to transmit mechanical power for propulsion between components of a system.
- 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.