Triple
T6013368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bart De Wever |
E133886
|
entity |
| Predicate | hasPartisanRole |
P4354
|
FINISHED |
| Object | party leader |
—
|
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: party leader | Statement: [Bart De Wever, hasPartisanRole, party leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartisanRole Context triple: [Bart De Wever, hasPartisanRole, party leader]
-
A.
hasPoliticalRole
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
-
B.
isNonpartisanOffice
Indicates that the office or position is not affiliated with, controlled by, or contested along formal political party lines.
-
C.
participatesInPoliticsOf
Indicates involvement or active engagement by one entity in the political processes, affairs, or governance activities of another entity.
-
D.
roleInCongress
Indicates the specific position or function an individual holds within a legislative congress.
-
E.
partySystemRole
chosen
Indicates the specific functional role or capacity that a party assumes within a given system or context.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f528acc8190bc6943d812460b57 |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.