Triple
T6013335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bart De Wever |
E133886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Flemish nationalist politician |
C4273
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Flemish nationalist politician Context triple: [Bart De Wever, instanceOf, Flemish nationalist politician]
-
A.
Hungarian politician
A Hungarian politician is a public figure who participates in the governance and political decision-making processes of Hungary, typically by holding or seeking elected or appointed office at the local, regional, or national level.
-
B.
prime minister of Belgium
The prime minister of Belgium is the head of the federal government, responsible for leading the Council of Ministers, setting national policy priorities, and representing Belgium both domestically and internationally.
-
C.
Austrian statesman
An Austrian statesman is a political leader or public official from Austria who plays a significant role in shaping the nation's domestic and foreign policies through governance, diplomacy, and legislative influence.
-
D.
Belgian person
chosen
A Belgian person is an individual who holds Belgian nationality or strongly identifies with Belgium’s cultural, linguistic, and social heritage.
-
E.
Belgian federal government
The Belgian federal government is the central governing authority of Belgium, responsible for national policy areas such as defense, justice, social security, and federal finance, operating within a complex federal system that shares powers with regional and community governments.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 22, 2026, 4:06 p.m.