Triple
T34183661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beerse |
E876894
|
entity |
| Predicate | governingMajority |
P56764
|
FINISHED |
| Object | CD&V |
—
|
NE NERFINISHED |
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: CD&V | Statement: [Beerse, governingMajority, CD&V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingMajority Context triple: [Beerse, governingMajority, CD&V]
-
A.
majoritySeats
Indicates that one party or group holds more than half of the available seats in a governing or decision-making body.
-
B.
governedAsMinorityOrMajority
Indicates that an entity governed another entity while holding either a minority or majority position within a governing body or coalition.
-
C.
majorityPosition
Indicates that the referenced position is held by more than half of the relevant group or decision-making body.
-
D.
parliamentaryMajority
chosen
Indicates that a political party or coalition holds more than half the seats in a parliament, enabling it to control legislative decisions.
-
E.
parliamentaryMajorityType
Indicates the type or nature of the majority held in a parliamentary body (e.g., absolute, simple, qualified) in relation to a given context or decision.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00d8ba18808190976682088a02a9a8 |
completed | May 10, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_6a00d85fad64819084f424ec8ecd3b57 |
completed | May 10, 2026, 7:11 p.m. |
Created at: May 1, 2026, 1:55 a.m.