Triple
T667933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI WorldTour |
E12906
|
entity |
| Predicate | rankingSystem |
P7476
|
FINISHED |
| Object | points-based |
—
|
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: points-based | Statement: [UCI WorldTour, rankingSystem, points-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingSystem Context triple: [UCI WorldTour, rankingSystem, points-based]
-
A.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
B.
rankingBasis
chosen
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
C.
rankingCategory
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
-
D.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
-
E.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff921288190a2e5edb201ba69ee |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.