Triple
T22604920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surselva |
E566529
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Lumnezia |
—
|
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: Lumnezia | Statement: [Surselva, contains, Lumnezia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lumnezia Context triple: [Surselva, contains, Lumnezia]
-
A.
Lumnezia
chosen
Lumnezia is a municipality and valley region in the canton of Graubünden in southeastern Switzerland, known for its Romansh-speaking population and alpine landscape.
-
B.
Orsza
Orsza is the wartime pseudonym of Stanisław Broniewski, a Polish scoutmaster and resistance leader during World War II.
-
C.
Burzenland
Burzenland is a historic region in southeastern Transylvania, Romania, known for its medieval Saxon settlements, fortified churches, and strategic location in the Carpathian foothills.
-
D.
Belonia
Belonia is a small town in the South Tripura district of the Indian state of Tripura, near the India–Bangladesh border.
-
E.
Ladania
Ladania is a town located in the Madhubani district of the Indian state of Bihar.
- 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f162709d808190af83837104a190f9 |
completed | April 29, 2026, 1:44 a.m. |
Created at: April 17, 2026, 2:53 p.m.