Triple
T14145586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond Poulidor |
E350539
|
entity |
| Predicate | TourDeFranceSecondPlaces |
P112989
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Raymond Poulidor, TourDeFranceSecondPlaces, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TourDeFranceSecondPlaces Context triple: [Raymond Poulidor, TourDeFranceSecondPlaces, 3]
-
A.
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.
-
B.
GrandTour
Indicates a comprehensive, often extended journey or series of visits undertaken to explore multiple places, typically for cultural, educational, or experiential purposes.
-
C.
TourDeFranceOverallWins
Indicates the number of times an entity has won the overall general classification of the Tour de France.
-
D.
TourDeFranceWins
Indicates the number of times an entity has won the Tour de France cycling race.
-
E.
cyclingRoadRaceVenue
Indicates that a location serves as the venue where a cycling road race event takes place.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de612266248190a8591b646fe30ae6 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:53 a.m.