Triple
T22836323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladin people |
E565956
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Fascian 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: Fascian Ladin | Statement: [Ladin people, hasDialect, Fascian Ladin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fascian Ladin Context triple: [Ladin people, hasDialect, Fascian 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.
Cimbro
Cimbro is a small frazione (hamlet) of the municipality of Vergiate in the Lombardy region of northern Italy.
-
D.
South Picene language
The South Picene language is an extinct Italic language once spoken in central Italy, known primarily from a small corpus of archaic inscriptions.
-
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_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.