Triple
T38149125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson Touring family |
E952701
|
entity |
| Predicate | typicalHandlebarPosition |
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 family, typicalHandlebarPosition, upright riding position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHandlebarPosition Context triple: [Harley-Davidson Touring family, typicalHandlebarPosition, upright riding position]
-
A.
handlebarType
Indicates the specific style or design of handlebars associated with an entity.
-
B.
handlebarHeight
Indicates the height of a bicycle’s handlebars relative to a reference point, such as the ground or the bike frame.
-
C.
hasHandlebarFairing
Indicates that an object is equipped with a fairing specifically mounted on or integrated into its handlebars.
-
D.
bicycleType
Indicates the specific kind or category of bicycle associated with an entity.
-
E.
ridingPosition
chosen
Indicates the relative physical placement or posture of an entity while it is riding or being carried by another entity.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.