Triple
T6668426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Moroccan Amazigh |
E151663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned language variety |
C8179
|
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: planned language variety Context triple: [Standard Moroccan Amazigh, instanceOf, planned language variety]
-
A.
constructed language variety
chosen
A constructed language variety is a deliberately designed form of language—such as a dialect, sociolect, or register—created or modified for specific purposes, contexts, or communities rather than arising solely through natural linguistic evolution.
-
B.
standardized language variety
A standardized language variety is a codified form of a language that has been deliberately regulated and accepted as the norm for public, official, and educational use within a speech community.
-
C.
pluricentric language variety
A pluricentric language variety is a form of a language that has multiple standardized national or regional norms, each with its own codified rules and prestige within different speech communities.
-
D.
macrolanguage variety
A macrolanguage variety is a specific linguistic form or set of forms that functions as one distinguishable member within a broader macrolanguage encompassing multiple closely related or mutually recognized language varieties.
-
E.
modern language variety
A modern language variety is a contemporary form or version of a language, distinguished by its unique features in vocabulary, grammar, pronunciation, and usage within a specific community or context.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:02 p.m.