Triple
T18472279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish parliamentary elections |
E451330
|
entity |
| Predicate | typicalGovernmentOutcome |
P11286
|
FINISHED |
| Object | coalition governments |
—
|
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: coalition governments | Statement: [Finnish parliamentary elections, typicalGovernmentOutcome, coalition governments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGovernmentOutcome Context triple: [Finnish parliamentary elections, typicalGovernmentOutcome, coalition governments]
-
A.
governmentOutcome
Indicates the result, consequence, or effect produced by a government’s decisions, actions, or policies.
-
B.
politicalOutcome
chosen
Indicates the result or consequence of a political process, decision, event, or interaction.
-
C.
governsOutcome
Indicates that one entity has decisive control or influence over the result or consequence affecting another entity.
-
D.
implementedGovernmentType
Indicates the specific form of government that has been put into practice or adopted by an entity.
-
E.
laterGovernmentType
Indicates that one government type succeeds or replaces another at a later point in time.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53060ae2c8190bf0821bb0ea5bd59 |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.