Triple
T32035028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klaus Groth |
E818067
|
entity |
| Predicate | hasParticularDialect |
P198390
|
FINISHED |
| Object | Holsteinisch Low German |
—
|
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: Holsteinisch Low German | Statement: [Klaus Groth, hasParticularDialect, Holsteinisch Low German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticularDialect Context triple: [Klaus Groth, hasParticularDialect, Holsteinisch Low German]
-
A.
hasDialects
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
-
B.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
C.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
-
D.
hasPrimaryLanguageDialect
Indicates that an entity’s main or default language is a specific dialect of a broader language.
-
E.
hasDialectalCounterpart
Indicates that one linguistic form has a corresponding equivalent or variant in another dialect.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: May 1, 2026, 12:18 a.m.