Triple
T31664835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Korean orthography |
E808097
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | language regulation |
C31860
|
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 regulation Context triple: [Standard Korean orthography, instanceOf, language regulation]
-
A.
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.
-
B.
language policy
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.
-
C.
linguistic law
A linguistic law is a systematic, recurrent pattern or regularity governing changes or structures in language across time, dialects, or contexts.
-
D.
legal language
Legal language is a specialized, formalized way of writing and speaking used in laws, contracts, and court documents, characterized by precise terminology, complex structure, and an emphasis on minimizing ambiguity.
-
E.
regulations
chosen
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:58 p.m.