Triple
T16057748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trials 26-inch |
E389525
|
entity |
| Predicate | typicalRiderPosition |
P88193
|
FINISHED |
| Object | standing on pedals |
—
|
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: standing on pedals | Statement: [Trials 26-inch, typicalRiderPosition, standing on pedals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRiderPosition Context triple: [Trials 26-inch, typicalRiderPosition, standing on pedals]
-
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.
typicalRiderEmotion
Indicates the characteristic or commonly experienced emotion that a rider typically feels in the context of a particular riding situation or activity.
-
D.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
E.
typicalPositionType
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.