Triple
T1713290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian party system |
E37232
|
entity |
| Predicate | coalitionsFormedAt |
P32246
|
FINISHED |
| Object | federal level |
—
|
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: federal level | Statement: [Belgian party system, coalitionsFormedAt, federal level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coalitionsFormedAt Context triple: [Belgian party system, coalitionsFormedAt, federal level]
-
A.
formedByCoalition
Indicates that something (such as a group, government, or organization) came into existence through the alliance or joint effort of multiple distinct parties or factions.
-
B.
coalitionType
Indicates the specific kind or category of coalition relationship that exists between the involved entities.
-
C.
coalitionPotential
Indicates the potential or likelihood that two or more entities can form a cooperative alliance or coalition.
-
D.
governsInCoalition
Indicates that an entity exercises governing authority jointly with one or more partners as part of a political coalition.
-
E.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
- F. None of above. chosen
Provenance (4 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab752034348190a1cc20955ed24f6f |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:30 p.m.