Triple

T5291440
Position Surface form Disambiguated ID Type / Status
Subject Norwegian throne E119749 entity
Predicate constitutionalLimitOnPowers P18971 FINISHED
Object yes 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: yes | Statement: [Norwegian throne, constitutionalLimitOnPowers, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: constitutionalLimitOnPowers
Context triple: [Norwegian throne, constitutionalLimitOnPowers, yes]
  • A. constitutionalLimit chosen
    Indicates that there is a restriction or boundary imposed by a constitution on the powers, actions, or rights involved in the relationship.
  • B. constitutionalPower
    Indicates that an entity holds authority or rights granted and defined by a constitution in relation to another entity or domain of action.
  • C. constitutionalPowersExercisedBy
    Indicates that certain powers or authorities defined by a constitution are carried out or exercised by a specified actor or institution.
  • D. constitutionalFunction
    Indicates that an entity serves a role, duty, or purpose as defined or required by a constitution or foundational governing framework.
  • E. constitutionalCategory
    Indicates the classification of something according to its constitutional or structural type or category.
  • 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_69bd446de5648190b313a90bd96730d2 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd8682d18c8190bbb35cc75c8a7c12 completed March 20, 2026, 5:40 p.m.
PD Predicate disambiguation batch_69bd844dfdac819086efedd1cbebff84 completed March 20, 2026, 5:30 p.m.
Created at: March 20, 2026, 1:52 p.m.