Triple
T8959527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brabant |
E213565
|
entity |
| Predicate | modernRegionalLanguage |
P10892
|
FINISHED |
| Object | Brabantian dialects |
—
|
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: Brabantian dialects | Statement: [Brabant, modernRegionalLanguage, Brabantian dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernRegionalLanguage Context triple: [Brabant, modernRegionalLanguage, Brabantian dialects]
-
A.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
B.
regionOfMajorLanguage
Indicates the geographic region where a particular language is predominantly spoken or holds major usage.
-
C.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
-
D.
historicalLanguageRegion
Indicates that a language was historically spoken or used within a particular geographic region, regardless of its current status there.
-
E.
motherTongueRegion
Indicates the geographic region where an entity’s native or primary language is predominantly spoken or originates.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc672b12b48190a9d964f79b96d237 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.