Triple
T567492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Constitution |
E13586
|
entity |
| Predicate | preambleTextBegins |
P1037
|
FINISHED |
| Object | We the people of Alaska |
—
|
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: We the people of Alaska | Statement: [Alaska Constitution, preambleTextBegins, We the people of Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preambleTextBegins Context triple: [Alaska Constitution, preambleTextBegins, We the people of Alaska]
-
A.
preambleBeginsWith
chosen
Indicates that the preamble of a document or text starts with a specified substring, phrase, or content.
-
B.
preamblePresent
Indicates that a document, statement, or agreement includes an introductory preamble section.
-
C.
preambleRecalls
Indicates that a preamble references or brings back into consideration a prior statement, event, or context.
-
D.
pretext
Indicates that one party uses a stated reason or excuse to conceal their true motive for an action or decision.
-
E.
beganWith
Indicates that one event, process, or state started with or was initiated by another specified event, process, or state.
- 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.