Triple
T26864976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boechout |
E676439
|
entity |
| Predicate | hasGoverningMajority |
P17177
|
FINISHED |
| Object | Vooruit |
—
|
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: Vooruit | Statement: [Boechout, hasGoverningMajority, Vooruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoverningMajority Context triple: [Boechout, hasGoverningMajority, Vooruit]
-
A.
hasMajority
Indicates that one entity holds more than half of the total share, control, or quantity in relation to another entity or set.
-
B.
hasMajorityOf
Indicates that one entity possesses or controls more than half of the total quantity, members, or share of another entity.
-
C.
hasMajorityIn
chosen
Indicates that one entity holds more than half of the control, ownership, or representation within another entity or group.
-
D.
votedWithMajorityIn
Indicates that an entity cast its vote in alignment with the majority decision within a given voting event or body.
-
E.
heldByMajority
Indicates that something (such as a position, opinion, or ownership) is possessed or supported by more than half of the relevant group or participants.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:28 a.m.