Triple
T38419077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werkendam (historical municipality) |
E903177
|
entity |
| Predicate | usedRegionalDialect |
P1762
|
FINISHED |
| Object | Brabantic |
—
|
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: Brabantic | Statement: [Werkendam (historical municipality), usedRegionalDialect, Brabantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRegionalDialect Context triple: [Werkendam (historical municipality), usedRegionalDialect, Brabantic]
-
A.
regionalDialect
chosen
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or region.
-
C.
usesSlangFrom
Indicates that one entity incorporates or employs slang expressions originating from another entity or source.
-
D.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
-
E.
hasDialectalOriginOf
Indicates that something originates from or is derived from a particular dialect.
- 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.