Triple

T7592560
Position Surface form Disambiguated ID Type / Status
Subject Norwegian politics E179773 entity
Predicate usesFixedTermParliament P75282 FINISHED
Object true 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: true | Statement: [Norwegian politics, usesFixedTermParliament, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesFixedTermParliament
Context triple: [Norwegian politics, usesFixedTermParliament, true]
  • A. hasFixedTermElections chosen
    Indicates that elections for a given office or body occur at predetermined, regular intervals rather than being called flexibly or at variable times.
  • B. parliamentaryTerm
    Indicates the specific legislative session or fixed period of time during which a parliament is formally in office and exercises its authority.
  • C. parliamentaryTermType
    Indicates the specific category or classification of a parliamentary term within a legislative or governmental context.
  • D. parliamentaryStatus
    Indicates the relationship of whether and how an entity is formally recognized or holds standing within a parliamentary system or body.
  • E. usesParliament
    Indicates that one entity conducts its legislative or decision‑making processes through a parliamentary body or system.
  • 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_69c69f335248819093c1006f30513708 completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c6f9b92c348190b547f0aacfb8d6be completed March 27, 2026, 9:42 p.m.
PD Predicate disambiguation batch_69c6f4e2e42c8190afc802c4796c9cc2 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:53 p.m.