Triple
T3698684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amstel Gold Race |
E78519
|
entity |
| Predicate | hasClimbsCount |
P49463
|
FINISHED |
| Object | 30+ categorized climbs |
—
|
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: 30+ categorized climbs | Statement: [Amstel Gold Race, hasClimbsCount, 30+ categorized climbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbsCount Context triple: [Amstel Gold Race, hasClimbsCount, 30+ categorized climbs]
-
A.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
B.
climbingStatus
Indicates the current state or condition of an entity with respect to a climbing activity or process (e.g., whether it is climbing, has climbed, or is not climbing).
-
C.
climbedBy
Indicates that something is ascended or scaled by an agent or entity.
-
D.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
E.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc512ba188190a15bcacafac3f476 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb903be308190a8f1925f99e67c68 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:26 p.m.