Triple
T24382779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combin de Grafeneire |
E614657
|
entity |
| Predicate | hasSummitInMassif |
P91967
|
FINISHED |
| Object | Combin de Valsorey |
—
|
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: Combin de Valsorey | Statement: [Combin de Grafeneire, hasSummitInMassif, Combin de Valsorey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitInMassif Context triple: [Combin de Grafeneire, hasSummitInMassif, Combin de Valsorey]
-
A.
hasMassif
Indicates that something possesses or is associated with a specific massif, typically a large, distinct section of a mountain range.
-
B.
hasSummitIn
chosen
Indicates that an entity (such as a mountain or organization) has its summit or peak located within a specified place or region.
-
C.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
-
D.
isAlpineSummit
Indicates that the subject is a mountain summit located within an alpine (high-mountain) environment.
-
E.
hasHigherSummit
Indicates that one entity’s summit is higher in elevation than another entity’s 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293dcd50c8190b242f68198343caa |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.