Triple
T19899366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haute-Ajoie |
E478239
|
entity |
| Predicate | formedByMergerOf |
P77
|
FINISHED |
| Object | Chevenez |
—
|
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: Chevenez | Statement: [Haute-Ajoie, formedByMergerOf, Chevenez]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chevenez Context triple: [Haute-Ajoie, formedByMergerOf, Chevenez]
-
A.
Chevenez
chosen
Chevenez is a village in the Ajoie region of the canton of Jura in northwestern Switzerland.
-
B.
Chevenoz
Chevenoz is a small rural commune in the Haute-Savoie department of southeastern France, situated in the Alpine Vallée d’Abondance near the Swiss border.
-
C.
Cugny
Cugny is a locality within the municipality of Bernex in the canton of Geneva, Switzerland.
-
D.
Olbreuse
Olbreuse is a small locality in western France historically notable as the ancestral seat of the noble d’Olbreuse family.
-
E.
Tiffauges
Tiffauges is a historic commune in western France, known for its medieval castle and scenic setting along the Sèvre Nantaise river.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6593fbb348190afa7acf45af406ed |
completed | April 20, 2026, 4:50 p.m. |
Created at: April 10, 2026, 1:52 p.m.