Triple
T2773661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle High German |
E61516
|
entity |
| Predicate | glottoStatus |
P28208
|
FINISHED |
| Object | treated as historical variety of German |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: treated as historical variety of German | Statement: [Middle High German, glottoStatus, treated as historical variety of German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glottoStatus Context triple: [Middle High German, glottoStatus, treated as historical variety of German]
-
A.
glottologStatus
chosen
Indicates the classification or status of a language or dialect as defined in the Glottolog database.
-
B.
glottocode
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
-
C.
glottoCategory
Indicates the linguistic classification or type (such as language family, subgroup, or category) to which a language or dialect is assigned.
-
D.
languageEndangermentStatus
Indicates the degree to which a language is at risk of falling out of use or becoming extinct.
-
E.
ISO639_3Status
Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
- F. None of above.
Provenance (3 batches)
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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.