Triple
T567484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Constitution |
E13586
|
entity |
| Predicate | draftingEnded |
P2818
|
FINISHED |
| Object | 1956 |
—
|
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 | Statement: [Alaska Constitution, draftingEnded, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: draftingEnded Context triple: [Alaska Constitution, draftingEnded, 1956]
-
A.
draftingStarted
Indicates that the process of creating an initial version or draft of something has begun.
-
B.
draftingPeriod
Indicates the time span during which a document, plan, or agreement is being written, revised, or prepared before it is finalized.
-
C.
draft
Indicates that one entity prepares an initial or preliminary version of something, typically a document, plan, or design, which may be revised later.
-
D.
draftType
Indicates the specific category or kind of draft associated with an entity or document (e.g., initial, revised, or final draft).
-
E.
concludedAt
chosen
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
- 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.