Triple
T14401674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Mansi |
E357086
|
entity |
| Predicate | isPrimaryDialectOf |
P73835
|
FINISHED |
| Object | Mansi language |
—
|
LITERAL 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: Mansi language | Statement: [Northern Mansi, isPrimaryDialectOf, Mansi language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryDialectOf Context triple: [Northern Mansi, isPrimaryDialectOf, Mansi language]
-
A.
isBasedOnDialect
Indicates that something (such as a language variety, system, or representation) is derived from, structured around, or primarily influenced by a particular dialect.
-
B.
hasDialectCounterpart
Indicates that one linguistic form or expression has a corresponding equivalent in another dialect.
-
C.
consideredDialectOf
chosen
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
D.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
E.
isDialectGroupOf
Indicates that one linguistic variety is a dialect group or cluster belonging to a broader language or language family.
- F. None of above.
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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de908500048190bb6a20fe318d5c62 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.