Triple
T906145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ain River |
E19552
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Jura |
E16904
|
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: Jura | Statement: [Ain River, region, Jura]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jura Context triple: [Ain River, region, Jura]
-
A.
Jura
Jura is a remote, sparsely populated island in Scotland’s Inner Hebrides, known for its rugged mountains, large red deer population, and the Jura whisky distillery.
-
B.
Jura
chosen
Jura is a predominantly French-speaking canton in northwestern Switzerland known for its Jura Mountains, watchmaking tradition, and strong regional identity.
-
C.
Broye
Broye is a river in western Switzerland that flows through the cantons of Fribourg and Vaud before emptying into Lake Neuchâtel.
-
D.
Rhône
Rhône is a department in eastern France named after the Rhône River, known for its capital city Lyon and its significant role in the country's economic and cultural life.
-
E.
Alpine Rhine
The Alpine Rhine is the upper stretch of the Rhine River flowing through the Alpine region, forming part of the border between Switzerland, Liechtenstein, and Austria.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2cc85a08190bc8186eb9ed1fa38 |
completed | March 1, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acce513848819094ad79eea2a53172 |
completed | March 8, 2026, 1:18 a.m. |
Created at: March 1, 2026, 7:39 p.m.