Triple
T16180964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MotoE World Championship |
E392680
|
entity |
| Predicate | hasChampionshipType |
P10813
|
FINISHED |
| Object | riders championship |
—
|
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: riders championship | Statement: [MotoE World Championship, hasChampionshipType, riders championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionshipType Context triple: [MotoE World Championship, hasChampionshipType, riders championship]
-
A.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
B.
championshipFor
chosen
Indicates that a championship event or title is held, awarded, or designated for a particular competition, season, or category.
-
C.
championshipHeld
Indicates that a championship event took place or was hosted at a particular time and/or location.
-
D.
hasChampionshipMatch
Indicates that an entity is associated with a specific championship-level match, typically as an organizer, participant, or host.
-
E.
supportsChampionshipsOf
Indicates that one entity provides backing, resources, or endorsement for the championships associated with 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205c92b48190b7125dbbcff3662e |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.