Triple
T15409516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collonges |
E368546
|
entity |
| Predicate | hasDemonym |
P191
|
FINISHED |
| Object | Collongeois |
E369512
|
NE 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: Collongeois | Statement: [Collonges, hasDemonym, Collongeois]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Collongeois Context triple: [Collonges, hasDemonym, Collongeois]
-
A.
Val d’Hérens
Val d’Hérens is a picturesque alpine valley in the Swiss canton of Valais, known for its traditional villages, dramatic peaks, and well-preserved rural culture.
-
B.
Broye-Vully
Broye-Vully is an administrative district in the canton of Vaud in western Switzerland, known for its rural landscapes, agriculture, and wine-producing areas.
-
C.
La Bresse
La Bresse is a French mountain town in northeastern France known for its ski resort and outdoor activities in the Vosges.
-
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.
Collonge
chosen
Collonge is a locality within the municipality of Collonge-Bellerive in the canton of Geneva, Switzerland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea4f13c819085d26fd32b5dca6f |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff135d65988190b35392bdf1e45985 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:20 a.m.