Triple
T11420034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson Touring |
E270593
|
entity |
| Predicate | typicalRidingPosition |
P88193
|
FINISHED |
| Object | upright riding position |
—
|
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: upright riding position | Statement: [Harley-Davidson Touring, typicalRidingPosition, upright riding position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRidingPosition Context triple: [Harley-Davidson Touring, typicalRidingPosition, upright riding position]
-
A.
ridingPosition
chosen
Indicates the relative physical placement or posture of an entity while it is riding or being carried by another entity.
-
B.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
C.
supportsRiderPosition
Indicates that one entity provides a stable or appropriate base or configuration that maintains or accommodates the rider’s body position.
-
D.
typicalSeat
Indicates the usual or standard seating position or location associated with an entity in a given context.
-
E.
hasSeatingPose
Indicates that an entity is in a seated posture or arrangement, specifying how it is positioned while sitting.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b20ce08190befc98379b879985 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.