Triple
T4120324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giro di Lombardia |
E92594
|
entity |
| Predicate | typicalWinnerProfile |
P52161
|
FINISHED |
| Object | climber |
—
|
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: climber | Statement: [Giro di Lombardia, typicalWinnerProfile, climber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWinnerProfile Context triple: [Giro di Lombardia, typicalWinnerProfile, climber]
-
A.
positionOfTypicalWinners
Indicates the usual or most common placement or ranking that winners occupy in a given context or competition.
-
B.
typicalCandidate
Indicates that an entity is a standard or representative example of what is usually considered a candidate in a given context.
-
C.
winnerType
chosen
Indicates the category or kind of winner associated with an event, competition, or outcome.
-
D.
winnerRepresents
Indicates that the winner of a competition or contest serves as a representative for a particular group, organization, or entity.
-
E.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.