Triple
T7111881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Order 13166 |
E165725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | language access policy |
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 access policy Context triple: [Executive Order 13166, instanceOf, language access policy]
-
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 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.
-
C.
language museum
A language museum is a curated space, physical or virtual, that preserves, exhibits, and interprets the history, diversity, structure, and cultural significance of human languages.
-
D.
official language
An official language is a language that a government designates for use in its legal, administrative, and public communication functions within a country or region.
-
E.
language use in a territory
The conceptual class "language use in a territory" represents how one or more languages are distributed, practiced, and function within a specific geographic or political area, including patterns of speakers, domains of use, and sociolinguistic dynamics.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:43 p.m.