Triple
T6877903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1917 Norwegian language reform |
E158716
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | language reform |
C13977
|
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: language reform Context triple: [1917 Norwegian language reform, instanceOf, language reform]
-
A.
language policy
chosen
Language policy is the set of deliberate decisions, principles, and regulations by which authorities or institutions influence the status, use, structure, and learning of one or more languages within a society.
-
B.
language revitalization project
A language revitalization project is an organized, community-centered effort to document, teach, and promote the use of an endangered or marginalized language to ensure its continued transmission and everyday use.
-
C.
legal reform
Legal reform is the process of reviewing, amending, and modernizing laws and legal institutions to better reflect current societal values, address injustices, and improve the effectiveness of the legal system.
-
D.
language regulator
A language regulator is an entity or institution that oversees, standardizes, and guides the usage, evolution, and norms of a language within a community or region.
-
E.
phonological change
Phonological change is the systematic alteration of a language’s sound patterns over time, affecting how words are pronounced and sometimes how they are represented in writing.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:22 p.m.