Triple
T3768878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI WorldTeams |
E82746
|
entity |
| Predicate | mainCompetitionFormat |
P2440
|
FINISHED |
| Object | stage races and one-day races |
—
|
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: stage races and one-day races | Statement: [UCI WorldTeams, mainCompetitionFormat, stage races and one-day races]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCompetitionFormat Context triple: [UCI WorldTeams, mainCompetitionFormat, stage races and one-day races]
-
A.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
replacedCompetitionFormat
Indicates that one competition format was substituted for and took the place of another competition format.
-
C.
affectedCompetitionFormat
Indicates that one entity caused a change or influence on the structure, rules, or format of a competition.
-
D.
typeOfCompetition
chosen
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
E.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2d4b848190bf63fb3ed5d3b2d9 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.