Triple
T14483194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet-Den Uyl |
E359161
|
entity |
| Predicate | numberOfPartiesInCoalition |
P34865
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Cabinet-Den Uyl, numberOfPartiesInCoalition, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPartiesInCoalition Context triple: [Cabinet-Den Uyl, numberOfPartiesInCoalition, 5]
-
A.
governsInCoalition
Indicates that an entity exercises governing authority jointly with one or more partners as part of a political coalition.
-
B.
hasNumberOfParties
chosen
Indicates the total count of distinct parties or participants involved in a given relationship, agreement, or event.
-
C.
majorPartyInLosingCoalition
Indicates that a major political party is a member of a coalition that ultimately loses (e.g., an election, vote, or contest for power).
-
D.
majorPartyInWinningCoalition
Indicates that a major political party is a member of the coalition that successfully forms the governing majority or wins the election.
-
E.
memberOfPoliticalCoalition
Indicates that an entity belongs to or participates as a constituent member in a specific political coalition.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924d7f4c8190b1f62b5ffe1ff649 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.