Triple
T18658921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional laws of Sardinia on linguistic heritage |
E456138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | language policy instrument |
C8592
|
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 policy instrument Context triple: [Regional laws of Sardinia on linguistic heritage, instanceOf, language policy instrument]
-
A.
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.
-
B.
cultural policy instrument
chosen
A cultural policy instrument is a deliberate tool, mechanism, or measure used by public authorities or institutions to influence, support, regulate, or shape cultural activities, expressions, and sectors in line with specific policy goals.
-
C.
cultural policy instrument
A cultural policy instrument is a deliberate tool or mechanism—such as funding schemes, regulations, incentives, or programs—used by public authorities to shape, support, or influence cultural production, distribution, and participation.
-
D.
policy development instrument
A policy development instrument is a structured tool, method, or mechanism used to design, analyze, and refine public or organizational policies to achieve specific objectives.
-
E.
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.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.