Triple
T9273567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20-Year Strategy for the Irish Language 2010–2030 |
E222888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national language strategy |
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: national language strategy Context triple: [20-Year Strategy for the Irish Language 2010–2030, instanceOf, national language strategy]
-
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.
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.
-
C.
national policy framework
A national policy framework is a structured set of overarching principles, goals, and guidelines that coordinate and align government actions, laws, and programs across sectors to achieve long-term national objectives.
-
D.
national initiative
A national initiative is a coordinated, large-scale program or policy effort undertaken at the country level to address a significant public issue or achieve a strategic national goal.
-
E.
national artificial intelligence strategy
A national artificial intelligence strategy is a government’s comprehensive plan that sets priorities, policies, and investments to guide the development, deployment, and governance of AI technologies for economic, social, and security objectives.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:33 p.m.