Triple
T5159570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French-speaking Community of Belgium |
E116400
|
entity |
| Predicate | hasParliamentType |
P6051
|
FINISHED |
| Object | unicameral parliament |
—
|
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: unicameral parliament | Statement: [French-speaking Community of Belgium, hasParliamentType, unicameral parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParliamentType Context triple: [French-speaking Community of Belgium, hasParliamentType, unicameral parliament]
-
A.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
B.
hasParliamentaryBodySeatType
Indicates the specific type or category of seat that an entity holds within a parliamentary body.
-
C.
parliamentaryGroupType
Indicates the specific kind or category of parliamentary group to which an entity belongs.
-
D.
typeOfParliamentaryBody
chosen
Indicates the specific kind or classification of a parliamentary body that an entity represents (e.g., lower house, upper house, unicameral chamber).
-
E.
containsParliament
Indicates that one political or administrative entity includes a parliament within its structure or jurisdiction.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.