Triple
T7479410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | district of Görlitz |
E176711
|
entity |
| Predicate | minorityLanguageRegion |
P2267
|
FINISHED |
| Object | Upper Sorbian |
—
|
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: Upper Sorbian | Statement: [district of Görlitz, minorityLanguageRegion, Upper Sorbian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorityLanguageRegion Context triple: [district of Görlitz, minorityLanguageRegion, Upper Sorbian]
-
A.
regionOfMajorLanguage
Indicates the geographic region where a particular language is predominantly spoken or holds major usage.
-
B.
isOfficialMinorityLanguageIn
chosen
Indicates that a language has formal, legally recognized minority-language status within a specified political or geographic entity.
-
C.
ethnoLinguisticRegionOf
Indicates that a region is defined or characterized by the shared ethnic and linguistic identity of the group associated with it.
-
D.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
E.
linguisticMinorityIn
Indicates that a group or population constitutes a linguistic minority within a specified geographic or political region.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4f13f548190a8cc59165735b30e |
completed | March 27, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.