Triple
T22371780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolomite valleys |
E553056
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | 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: Ladin | Statement: [Dolomite valleys, hasLanguage, Ladin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ladin Context triple: [Dolomite valleys, hasLanguage, Ladin]
-
A.
Ladinian
The Ladinian is a Middle Triassic geologic age and stage characterized by significant marine sedimentation and the diversification of early Mesozoic life.
-
B.
Ladin language
chosen
Ladin language is a Rhaeto-Romance language spoken primarily in the Dolomite mountain region of northern Italy.
-
C.
Segestani
The Segestani were an ancient Illyrian tribe that inhabited the region around the city of Siscia in what is now central Croatia.
-
D.
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.
-
E.
Luganese
Luganese is a region in the southern part of the Swiss canton of Ticino centered around the city of Lugano.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15804f1b08190b57689e6afb615a0 |
completed | April 29, 2026, 12:59 a.m. |
Created at: April 16, 2026, 8:44 p.m.