Triple
T14126069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Närke |
E340035
|
entity |
| Predicate | historicalDialectRegion |
P29176
|
FINISHED |
| Object | Närke dialect |
—
|
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: Närke dialect | Statement: [Närke, historicalDialectRegion, Närke dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDialectRegion Context triple: [Närke, historicalDialectRegion, Närke dialect]
-
A.
historicalDialect
Indicates that one dialect is a historically earlier or ancestral form of another dialect.
-
B.
historicalLanguageRegion
chosen
Indicates that a language was historically spoken or used within a particular geographic region, regardless of its current status there.
-
C.
historicalPrestigeDialect
Indicates that a dialect has traditionally been regarded as prestigious or high-status within a historical or cultural context.
-
D.
regionalDialect
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
E.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6096976481909dc79066c5165a50 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.