Triple
T35541984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberdorf (Zürich) |
E1027084
|
entity |
| Predicate | localDialectName |
P184432
|
FINISHED |
| Object | Oberdorf |
—
|
NE NERFINISHED |
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: Oberdorf | Statement: [Oberdorf (Zürich), localDialectName, Oberdorf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localDialectName Context triple: [Oberdorf (Zürich), localDialectName, Oberdorf]
-
A.
localLanguageName
Indicates the name of a language as it is written or referred to in its own local or native form.
-
B.
modernLocalName
Indicates the current, locally used name or designation for an entity, as recognized in the present time.
-
C.
dominantDialect
Indicates that one dialect is the primary or most influential form of a language within a particular context or region.
-
D.
localeType
Indicates the classification or category of a locale (such as region, city, or venue type) that characterizes the kind of place involved in the relationship.
-
E.
locale
Indicates that one entity is the place, setting, or geographic area in which another entity exists, occurs, or is situated.
- F. None of above. chosen
Provenance (4 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:04 p.m.