Triple
T14482596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alto de Jaizkibel |
E359146
|
entity |
| Predicate | climbProfile |
P18720
|
FINISHED |
| Object | irregular with several steep ramps |
—
|
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: irregular with several steep ramps | Statement: [Alto de Jaizkibel, climbProfile, irregular with several steep ramps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbProfile Context triple: [Alto de Jaizkibel, climbProfile, irregular with several steep ramps]
-
A.
altitudeProfile
chosen
Indicates the variation of elevation or height along a path, route, or trajectory over distance or time.
-
B.
climbPerformance
Indicates how effectively or rapidly an entity ascends or gains altitude relative to conditions or expectations.
-
C.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
D.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
-
E.
coClimber
Indicates that two or more entities participate together in the same climbing activity or ascent.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924bc548819087a2f693840d7426 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.