Triple
T22901758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canavese dialect |
E568335
|
entity |
| Predicate | spokenIn |
P2266
|
FINISHED |
| Object | Canavese |
—
|
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: Canavese | Statement: [Canavese dialect, spokenIn, Canavese]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Canavese Context triple: [Canavese dialect, spokenIn, Canavese]
-
A.
Canavese
chosen
Canavese is a historical and geographical area in northern Italy known for its rolling hills, medieval castles, and renowned wine production within the Piedmont region.
-
B.
Piemontese
Piemontese is a Romance language spoken primarily in Italy’s Piedmont region, distinct from standard Italian and recognized for its own rich literary and cultural tradition.
-
C.
Canavese Piedmontese
Canavese Piedmontese is a regional variety of the Piedmontese language spoken in the Canavese area of northwestern Italy.
-
D.
Bergamasque
Bergamasque is a Gallo-Italic dialect spoken primarily in and around the city of Bergamo in northern Italy.
-
E.
Turinese Piedmontese
Turinese Piedmontese is the urban variety of the Piedmontese language traditionally spoken in and around the city of Turin in northwestern Italy.
- 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18016d8e481908fc47d003156b800 |
completed | April 29, 2026, 3:50 a.m. |
Created at: April 17, 2026, 3:41 p.m.