Triple

T567520
Position Surface form Disambiguated ID Type / Status
Subject Alaska Constitution E13586 entity
Predicate allowsConstitutionalConvention P15654 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: [Alaska Constitution, allowsConstitutionalConvention, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsConstitutionalConvention
Context triple: [Alaska Constitution, allowsConstitutionalConvention, yes]
  • A. convenedUnderConstitution
    Indicates that an assembly, body, or proceeding was formally brought into existence and organized according to the rules and authority of a specific constitution.
  • B. canAmendConstitution
    Indicates that an entity has the authority or power to modify or revise a constitution.
  • C. laterConstitutionalAct
    Indicates that one constitutional act occurs after another in time, establishing a later legal or constitutional measure relative to a prior one.
  • D. canAmendBills
    Indicates that an entity has the authority or ability to modify, revise, or propose changes to bills.
  • E. allowsDirectDemocracy
    Indicates that an entity provides mechanisms for citizens to directly participate in decision-making processes, such as through referendums or initiatives.
  • 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_69a4933edcf08190b35ecfd6014caee6 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49b02da148190b6a9bad3a22d8ec5 completed March 1, 2026, 8:01 p.m.
PD Predicate disambiguation batch_69a494c183b081909304944aa3d0fe8f completed March 1, 2026, 7:34 p.m.
PDg Predicate description generation batch_69a4985a2d08819090947895d9439e06 completed March 1, 2026, 7:49 p.m.
Created at: March 1, 2026, 7:33 p.m.