Triple
T3793481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eneco Tour |
E89711
|
entity |
| Predicate | uciRankingPoints |
P26152
|
FINISHED |
| Object | WorldTour points |
—
|
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: WorldTour points | Statement: [Eneco Tour, uciRankingPoints, WorldTour points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uciRankingPoints Context triple: [Eneco Tour, uciRankingPoints, WorldTour points]
-
A.
rankingPoints
chosen
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
B.
selectionRankingEndPoint
Indicates the position or boundary in an ordered list at which a selection or ranking process concludes.
-
C.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
D.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
E.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.