Triple
T37268690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson Rocker |
E924454
|
entity |
| Predicate | intendedRiderPosition |
P88193
|
FINISHED |
| Object | feet-forward 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: feet-forward riding position | Statement: [Harley-Davidson Rocker, intendedRiderPosition, feet-forward riding position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRiderPosition Context triple: [Harley-Davidson Rocker, intendedRiderPosition, feet-forward 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.
supportsRiderPosition
Indicates that one entity provides a stable or appropriate base or configuration that maintains or accommodates the rider’s body position.
-
C.
targetedPosition
Indicates a relationship where an action, influence, or focus is specifically directed toward a particular position, role, or location.
-
D.
bearerPosition
Indicates the spatial or positional relationship of a bearer (holder or carrier) relative to the item or entity it bears.
-
E.
rackPosition
Indicates the spatial placement or slot of an item within a rack or racking 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:15 p.m.