Triple
T10513273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont Aiguille |
E247968
|
entity |
| Predicate | summitUse |
P64977
|
FINISHED |
| Object | occasionally used for bivouacs by climbers |
—
|
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: occasionally used for bivouacs by climbers | Statement: [Mont Aiguille, summitUse, occasionally used for bivouacs by climbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitUse Context triple: [Mont Aiguille, summitUse, occasionally used for bivouacs by climbers]
-
A.
summitView
Indicates a vantage point or perspective that is obtained from the top or highest point of something, such as a mountain or structure.
-
B.
summitPractice
Indicates that an entity engages in or is associated with a practice, activity, or event related to a summit (such as a high-level meeting or peak-focused endeavor).
-
C.
summitCount
Indicates the number of summits or peak ascents associated with an entity.
-
D.
hasSummitUse
chosen
Indicates that something is designated for use specifically at or on a summit (e.g., the top of a mountain or peak).
-
E.
summitEnvironment
Indicates the environmental conditions or context present at the summit of a mountain or peak.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509ca214481909b3ed9265e7a6704 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.