Triple
T4357781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirzel |
E98591
|
entity |
| Predicate | primarySpokenDialect |
P41081
|
FINISHED |
| Object | Swiss 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: Swiss German | Statement: [Hirzel, primarySpokenDialect, Swiss German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySpokenDialect Context triple: [Hirzel, primarySpokenDialect, Swiss German]
-
A.
primaryLanguageVariety
chosen
Indicates the main dialect or specific variety of a language that an entity primarily uses.
-
B.
spokenPrimarilyOn
Indicates that something (typically a language or dialect) is used mainly for spoken communication in a particular context, region, or group.
-
C.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
D.
primaryLanguageOf
Indicates that a specified language is the main or official language used by a particular entity (such as a person, organization, or region).
-
E.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c7fa1881908bdc844a7142eb65 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.