Triple
T16210057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoncolan |
E393437
|
entity |
| Predicate | notableForCyclists |
P22
|
FINISHED |
| Object | long sustained steep sections |
—
|
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: long sustained steep sections | Statement: [Zoncolan, notableForCyclists, long sustained steep sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForCyclists Context triple: [Zoncolan, notableForCyclists, long sustained steep sections]
-
A.
notableRiderType
Indicates that an entity is notably associated with a particular type or category of rider (e.g., cyclist, jockey, driver).
-
B.
importanceInCycling
Indicates the degree to which something is considered significant, influential, or central within the context of cycling.
-
C.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
crossCountryCourseNotableFor
Indicates that a cross-country course is distinguished or recognized for a particular feature, quality, or characteristic.
-
E.
cyclingCategory
Indicates the classification or type of cycling activity or discipline associated with an 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22713282481909c7c0d0782213461 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.