Triple
T16597247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsa Rosa |
E403239
|
entity |
| Predicate | stageRace |
P123460
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Corsa Rosa, stageRace, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageRace Context triple: [Corsa Rosa, stageRace, true]
-
A.
stageRaceType
Indicates the specific category or format of a multi-stage race within a broader competition or event.
-
B.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
C.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
-
D.
GrandTour
Indicates a comprehensive, often extended journey or series of visits undertaken to explore multiple places, typically for cultural, educational, or experiential purposes.
-
E.
timeTrialStages
Indicates that the related stages of a race are conducted as time trials, where participants compete individually against the clock rather than directly against each other.
- F. None of above. chosen
Provenance (4 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d723c508190b5afbda5eec5abea |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.