Triple
T30521502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldSSP |
E776703
|
entity |
| Predicate | worldChampionshipStatus |
P109375
|
FINISHED |
| Object | FIM World Championship |
—
|
NE NERFINISHED |
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: FIM World Championship | Statement: [WorldSSP, worldChampionshipStatus, FIM World Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldChampionshipStatus Context triple: [WorldSSP, worldChampionshipStatus, FIM World Championship]
-
A.
worldChampionshipStatusEffectiveSeason
Indicates the specific season from which a competition or event is officially recognized as having world championship status.
-
B.
worldChampionshipStatusGrantedBy
chosen
Indicates that an entity has been officially granted world championship status by a particular governing body or authority.
-
C.
championshipStatus
Indicates the competitive or title-holding state of an entity within a championship or league context.
-
D.
worldChampionshipsOrganiser
Indicates that the subject is responsible for organizing or managing world championship events for the object.
-
E.
WorldChampionshipsEvent
Indicates an event that is part of, or constitutes, a world-level championship competition.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 29, 2026, 8:17 p.m.