Triple
T14469302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Mansi |
E358794
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Southern Mansi |
E363565
|
NE FINISHED |
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: Southern Mansi | Statement: [Eastern Mansi, relatedTo, Southern Mansi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Southern Mansi Context triple: [Eastern Mansi, relatedTo, Southern Mansi]
-
A.
Southern Mansi
chosen
Southern Mansi is a dialect of the Uralic Mansi language traditionally spoken by the Mansi people in parts of western Siberia.
-
B.
Eastern Mansi
Eastern Mansi is a dialect of the Uralic Mansi language traditionally spoken by Mansi communities in the eastern part of their historical territory in western Siberia.
-
C.
Northern Mansi
Northern Mansi is a primary dialect of the Uralic Mansi language spoken by the Mansi people in northern Russia.
-
D.
Western Mansi
Western Mansi is a dialect of the Mansi (Vogul) language spoken by the Mansi people in western Siberia.
-
E.
Southern Khanty
Southern Khanty is a dialectal variety of the Uralic Khanty language traditionally spoken by Khanty communities in the southern part of their historical territory in western Siberia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f969788190a5114f92d7159aae |
completed | April 14, 2026, 7:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5c018788190afad213c580d7072 |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:20 a.m.