Triple
T16561594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Classicissima |
E402350
|
entity |
| Predicate | hasSprintClimbsNearFinish |
P124058
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [La Classicissima, hasSprintClimbsNearFinish, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSprintClimbsNearFinish Context triple: [La Classicissima, hasSprintClimbsNearFinish, yes]
-
A.
hasNearbyClimb
Indicates that one location or entity is situated close to a climbable feature or climbing route.
-
B.
hasStaircaseToSummit
Indicates that there exists a staircase providing a direct route or access from a lower point to the summit of something.
-
C.
hasApproxElevationGainFt
Indicates that one entity is associated with an approximate amount of elevation gain, measured in feet, relative to another context or reference.
-
D.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
E.
hasClimbsCount
Indicates that an entity is associated with a specific number of climbs it has completed or is credited with.
- F. None of above. chosen
Provenance (4 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576eb63081908cb5dc6c0a8a13ac |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.