Triple
T33830642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | contact with Majangir |
E867088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical sociolinguistic phenomenon |
C12779
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical sociolinguistic phenomenon Context triple: [contact with Majangir, instanceOf, historical sociolinguistic phenomenon]
-
A.
linguistic phenomenon
chosen
A linguistic phenomenon is any observable pattern, behavior, or feature in language use or structure that can be systematically described and analyzed.
-
B.
historical sound change
Historical sound change is the systematic alteration of speech sounds in a language over time, resulting in predictable shifts in pronunciation patterns across generations.
-
C.
historical language
A historical language is a natural language studied in the context of its past stages, evolution, and usage within specific historical periods and societies.
-
D.
tool in historical linguistics
A tool in historical linguistics is any methodological or analytical instrument—such as sound laws, comparative word lists, or phylogenetic models—used to reconstruct language histories, relationships, and changes over time.
-
E.
historical language stage
A historical language stage is a distinct, temporally bounded phase in the development of a language, characterized by relatively stable structural features and documented through historical evidence.
- F. None of above.
Provenance (1 batch)
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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.