Triple
T19958004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supersport motorcycle |
E479736
|
entity |
| Predicate | targetRider |
P12077
|
FINISHED |
| Object | sport-oriented riders |
—
|
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: sport-oriented riders | Statement: [Supersport motorcycle, targetRider, sport-oriented riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRider Context triple: [Supersport motorcycle, targetRider, sport-oriented riders]
-
A.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
B.
intendedRiderExperience
Indicates the type or quality of experience that is planned or designed for a rider in the context of a ride or transportation service.
-
C.
testRiderFor
Indicates that a rider is being evaluated, examined, or assessed for a particular purpose, condition, or qualification.
-
D.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
E.
primaryRiders
chosen
Indicates that the referenced entities are the main or principal riders associated with a particular vehicle, trip, or ride-related event.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af1b32c81908ebe0e2570ec06a9 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.