Triple
T25070443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dano-Norwegian |
E627892
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical written language standard |
C4690
|
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: historical written language standard Context triple: [Dano-Norwegian, instanceOf, historical written language standard]
-
A.
historical language
A historical language is a natural language studied in the context of its past stages, evolution, and usage within specific historical periods and societies.
-
B.
historical language stage
A historical language stage is a distinct, temporally bounded phase in the development of a language, characterized by relatively stable structural features and documented through historical evidence.
-
C.
historical linguistic document
A historical linguistic document is a written or recorded artifact from the past that provides evidence about the language, its usage, and its evolution in a particular historical context.
-
D.
standardized language variety
chosen
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.
-
E.
classical language variety
A classical language variety is a historically prestigious, standardized form of a language, typically preserved in literature and formal contexts, that differs from its modern spoken descendants.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:10 a.m.