Triple
T16989757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamber of Representatives of Belgium |
E412160
|
entity |
| Predicate | languageGroups |
P3349
|
FINISHED |
| Object | Dutch-speaking group |
—
|
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: Dutch-speaking group | Statement: [Chamber of Representatives of Belgium, languageGroups, Dutch-speaking group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageGroups Context triple: [Chamber of Representatives of Belgium, languageGroups, Dutch-speaking group]
-
A.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
B.
languageGroupName
Indicates the name assigned to a particular language group or linguistic classification.
-
C.
hasLanguageGroup
chosen
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
D.
languageGroupAncestor
Indicates that one language group is an ancestor (historical or genealogical predecessor) of another language group in a language family.
-
E.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27fbaa0819099f79fc74d211647 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.