Triple
T17134837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI Road World Cup |
E415808
|
entity |
| Predicate | includedRaceCategory |
P118441
|
FINISHED |
| Object | monument classics |
—
|
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: monument classics | Statement: [UCI Road World Cup, includedRaceCategory, monument classics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedRaceCategory Context triple: [UCI Road World Cup, includedRaceCategory, monument classics]
-
A.
associatedWithRaceCategory
chosen
Indicates a relationship in which an entity is linked or assigned to a particular race category.
-
B.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
C.
raceRole
Indicates the specific role, position, or function an entity holds within a race or racing event.
-
D.
includesMixedSexRace
Indicates that the group or context involves individuals of more than one sex and more than one race.
-
E.
recognizedAsMinorityIn
Indicates that an entity is officially acknowledged or classified as belonging to a minority group within a specified context or jurisdiction.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02dca8881908efd73741397a207 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.