Triple
T35390762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col du Télégraphe |
E1022929
|
entity |
| Predicate | climbFinish |
P18072
|
FINISHED |
| Object | Col du Télégraphe summit |
—
|
NE NERFINISHED |
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: Col du Télégraphe summit | Statement: [Col du Télégraphe, climbFinish, Col du Télégraphe summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbFinish Context triple: [Col du Télégraphe, climbFinish, Col du Télégraphe summit]
-
A.
climbStart
Indicates the moment or event when an entity begins the action of climbing something.
-
B.
decisiveClimbIn
Indicates a climbing action in which the subject moves into or onto something in a firm, committed, and conclusive manner, leaving little doubt about the intention or outcome of the climb.
-
C.
climbPerformance
Indicates how effectively or rapidly an entity ascends or gains altitude relative to conditions or expectations.
-
D.
reachesSummit
chosen
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
E.
climbs
Indicates that an entity moves upward onto or up the surface of another entity, typically overcoming vertical or inclined distance.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.