Triple
T26188389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parco del Monviso |
E654892
|
entity |
| Predicate | mainPeak |
P122462
|
FINISHED |
| Object | Monviso |
—
|
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: Monviso | Statement: [Parco del Monviso, mainPeak, Monviso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPeak Context triple: [Parco del Monviso, mainPeak, Monviso]
-
A.
hasMainPeakElevation_m
Indicates the relationship that specifies the elevation, in meters, of the main or highest peak associated with an entity.
-
B.
otherMajorPeak
Indicates that one peak is another significant or prominent peak associated with, but distinct from, a given primary peak.
-
C.
hasMainMountain
chosen
Indicates that an entity is primarily associated with or characterized by a specific mountain as its main or most significant mountain.
-
D.
moreProminentSummit
Indicates that one summit is higher, more notable, or more significant than another in terms of prominence.
-
E.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 8:43 p.m.