Triple
T4665745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenva face |
E102840
|
entity |
| Predicate | summitsReachedByRoutes |
P18072
|
FINISHED |
| Object | Mont Blanc summit ridge |
—
|
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: Mont Blanc summit ridge | Statement: [Brenva face, summitsReachedByRoutes, Mont Blanc summit ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitsReachedByRoutes Context triple: [Brenva face, summitsReachedByRoutes, Mont Blanc summit ridge]
-
A.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
B.
totalAscent
Indicates the total cumulative elevation gained over the course of a movement, route, or activity.
-
C.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
D.
reachesSummit
chosen
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
E.
firstAscentOfHigherSummit
Indicates that the subject entity is the first recorded ascent of a summit that is higher than another referenced summit.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.