Triple
T10838494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aduard |
E255824
|
entity |
| Predicate | regionalLanguageSpoken |
P2982
|
FINISHED |
| Object | Gronings |
—
|
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: Gronings | Statement: [Aduard, regionalLanguageSpoken, Gronings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalLanguageSpoken Context triple: [Aduard, regionalLanguageSpoken, Gronings]
-
A.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
B.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
C.
recognizedRegionalLanguage
chosen
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
-
D.
regionOfMajorLanguage
Indicates the geographic region where a particular language is predominantly spoken or holds major usage.
-
E.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d747002b3081908726901ee83d8f38 |
completed | April 9, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.