Triple
T4013480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI Para-cycling World Championships |
E90699
|
entity |
| Predicate | isTopLevelCompetitionIn |
P18266
|
FINISHED |
| Object | para-cycling |
—
|
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: para-cycling | Statement: [UCI Para-cycling World Championships, isTopLevelCompetitionIn, para-cycling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTopLevelCompetitionIn Context triple: [UCI Para-cycling World Championships, isTopLevelCompetitionIn, para-cycling]
-
A.
isTopLevelLeagueIn
Indicates that a sports league is the highest (top-tier) competitive level within a specified country or region.
-
B.
primaryCompetitionLevel
chosen
Indicates the main or highest level of competition at which an entity primarily competes or operates.
-
C.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
D.
featuredCompetitionLevel
Indicates that a particular competition level is highlighted or given special prominence relative to other levels.
-
E.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.