Triple
T19055504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val di Cogne |
E466382
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Cogne (municipality) |
—
|
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: Cogne (municipality) | Statement: [Val di Cogne, contains, Cogne (municipality)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cogne (municipality) Context triple: [Val di Cogne, contains, Cogne (municipality)]
-
A.
Cogne
chosen
Cogne is a renowned alpine village in Italy’s Aosta Valley, known for its access to the Gran Paradiso National Park and its hiking, climbing, and cross-country skiing opportunities.
-
B.
Cugny
Cugny is a locality within the municipality of Bernex in the canton of Geneva, Switzerland.
-
C.
Cugy (Fribourg)
Cugy (Fribourg) is a municipality in the canton of Fribourg in western Switzerland.
-
D.
Gueugnon
Gueugnon is a small commune in eastern France known historically for its steel industry and location in the Bourgogne-Franche-Comté region.
-
E.
Saint-Cergue
Saint-Cergue is a Swiss mountain municipality in the canton of Vaud, known for its scenic Jura landscapes and outdoor recreational activities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc056b708190a2b84cbddf0fc2d9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 10, 2026, 12:03 p.m.