Triple
T22836321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladin people |
E565956
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Gherdëina Ladin |
—
|
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: Gherdëina Ladin | Statement: [Ladin people, hasDialect, Gherdëina Ladin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gherdëina Ladin Context triple: [Ladin people, hasDialect, Gherdëina Ladin]
-
A.
Gröden Ladin
Gröden Ladin is the Ladin language variety spoken in the Val Gardena (Gherdëina) region of the Dolomites in northern Italy.
-
B.
Ladin language
Ladin language is a Rhaeto-Romance language spoken primarily in the Dolomite mountain region of northern Italy.
-
C.
Savognin
Savognin is a Swiss mountain village and ski resort in the canton of Graubünden, known for its alpine scenery and outdoor recreation.
-
D.
Valtellinese
Valtellinese is a regional variety of the Lombard language spoken in the Valtellina valley of northern Italy.
-
E.
Gherdëina
chosen
Gherdëina is a Ladin dialect spoken in the Val Gardena region of the Dolomites in northern 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2f09608190bc8e465e53b39e2e |
completed | April 29, 2026, 3:42 a.m. |
Created at: April 17, 2026, 3:35 p.m.