Triple
T2435739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania German |
E52955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German language variety |
C243
|
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: German language variety Context triple: [Pennsylvania German, instanceOf, German language variety]
-
A.
medieval North Germanic language variety
A medieval North Germanic language variety is a historical form of a Scandinavian language spoken in Northern Europe during the Middle Ages, characterized by its distinct phonology, morphology, and vocabulary relative to both earlier Norse and later modern Scandinavian languages.
-
B.
Greek language variety
A Greek language variety is a distinct form of the Greek language, characterized by specific phonological, grammatical, lexical, and pragmatic features associated with particular regions, communities, or social groups.
-
C.
West Germanic language
chosen
A West Germanic language is a member of the Germanic branch of the Indo-European language family that evolved in western and central Europe, including languages such as English, German, and Dutch.
-
D.
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.
-
E.
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.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:43 p.m.