Triple

T877517
Position Surface form Disambiguated ID Type / Status
Subject Norwegian coalition governments E18955 entity
Predicate reasonForUse P21011 FINISHED
Object absence of single-party parliamentary majority 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: absence of single-party parliamentary majority | Statement: [Norwegian coalition governments, reasonForUse, absence of single-party parliamentary majority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForUse
Context triple: [Norwegian coalition governments, reasonForUse, absence of single-party parliamentary majority]
  • A. usedFor
    Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
  • B. selectionReason
    Indicates the reason or justification for choosing or selecting one entity over alternatives.
  • C. reasonForCreation
    Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
  • D. eligibleUses
    Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
  • E. designationUsedFor
    Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
  • 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_69a4938db1f081909bcd1ad2713b6096 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4acb06ea88190962502172d434eb4 completed March 1, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69a4aa8d47c081909b02a53e305ccf7a completed March 1, 2026, 9:07 p.m.
PDg Predicate description generation batch_69a4ab9634948190b25ea1b2e34df87d completed March 1, 2026, 9:11 p.m.
Created at: March 1, 2026, 7:39 p.m.