Triple
T15395173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richie Porte |
E368158
|
entity |
| Predicate | wonClassification |
P47643
|
FINISHED |
| Object | best young rider Giro d'Italia 2010 |
—
|
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: best young rider Giro d'Italia 2010 | Statement: [Richie Porte, wonClassification, best young rider Giro d'Italia 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonClassification Context triple: [Richie Porte, wonClassification, best young rider Giro d'Italia 2010]
-
A.
wonBy
Indicates that a contest, game, or competition is decided in favor of a particular participant or side.
-
B.
pointsClassificationWinner
chosen
Indicates that the subject is the winner of a competition or ranking based on accumulated points classification.
-
C.
wonAt
Indicates that one entity achieved victory or success in a specific event, competition, or context.
-
D.
wonFor
Indicates that one entity received an award, prize, or recognition specifically on behalf of or representing another entity.
-
E.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ac79081908ac79c0b3e7587ff |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.