Triple
T19099948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shroud (Le Linceul) |
E467504
|
entity |
| Predicate | bestClimbedIn |
P134368
|
FINISHED |
| Object | stable cold conditions |
—
|
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: stable cold conditions | Statement: [Shroud (Le Linceul), bestClimbedIn, stable cold conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestClimbedIn Context triple: [Shroud (Le Linceul), bestClimbedIn, stable cold conditions]
-
A.
highestPeakClimbed
Indicates the tallest mountain or peak that an entity has successfully climbed.
-
B.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
C.
notableClimbs
Indicates that the subject has completed or is associated with particularly significant or well-known climbing routes or ascents.
-
D.
isMostTopographicallyProminentIn
Indicates that an entity has the greatest topographic prominence within a specified area or group, exceeding that of all comparable entities.
-
E.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e36d279081908aeb472cd740c302 |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.