Triple
T31737750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyoming state law |
E810049
|
entity |
| Predicate | hasConstitutionAdopted |
P153231
|
FINISHED |
| Object | 1889 |
—
|
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: 1889 | Statement: [Wyoming state law, hasConstitutionAdopted, 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstitutionAdopted Context triple: [Wyoming state law, hasConstitutionAdopted, 1889]
-
A.
lastConstitutionAdopted
Indicates that a particular constitution was the most recently adopted constitution of a given political entity or jurisdiction.
-
B.
constitutionAdoptedIn
Indicates the event or relationship in which a constitution is formally adopted in a specific place or jurisdiction.
-
C.
constitutionAdopted
Indicates that a particular constitution has been formally accepted and put into effect by the relevant authority or polity.
-
D.
hasConstitutionApprovedInYear
chosen
Indicates that an entity’s constitution was formally approved in a specified year.
-
E.
earliestConstitutionAdopted
Indicates that one entity is the constitution that was adopted first in time among all constitutions associated with another entity.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a03142a3a7081909bcfb683b44e2217 |
completed | May 12, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_6a031400af808190a72abf095e96c151 |
completed | May 12, 2026, 11:50 a.m. |
Created at: April 30, 2026, 11:23 p.m.