Triple
T567486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Constitution |
E13586
|
entity |
| Predicate | ratifiedByVoters |
P1036
|
FINISHED |
| Object | 1956-04-24 |
—
|
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: 1956-04-24 | Statement: [Alaska Constitution, ratifiedByVoters, 1956-04-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ratifiedByVoters Context triple: [Alaska Constitution, ratifiedByVoters, 1956-04-24]
-
A.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
B.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or action.
-
C.
ratifiedOn
chosen
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
-
D.
hasElectoralVotes
Indicates that a political entity (such as a state or district) possesses a specified number of votes in an electoral system used to choose an officeholder.
-
E.
ratificationMethod
Indicates the process or formal procedure by which an agreement, decision, or document is officially approved and made valid.
- 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_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. |
Created at: March 1, 2026, 7:33 p.m.