Triple
T244783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of California |
E5012
|
entity |
| Predicate | firstConstitutionAdopted |
P2497
|
FINISHED |
| Object | 1849 |
—
|
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: 1849 | Statement: [Government of California, firstConstitutionAdopted, 1849]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstConstitutionAdopted Context triple: [Government of California, firstConstitutionAdopted, 1849]
-
A.
stateOfFirstRatification
Indicates the state in which an agreement, treaty, or document was first formally ratified.
-
B.
foundingDocument
Indicates that one entity serves as the official charter, constitution, or primary legal/organizational document that establishes or defines the other entity.
-
C.
dateOfConstitutionSigning
chosen
Indicates the date on which a constitution was formally signed or adopted.
-
D.
laterConstitutionalAct
Indicates that one constitutional act occurs after another in time, establishing a later legal or constitutional measure relative to a prior one.
-
E.
previousConstitutionRevised
Indicates that a prior constitution has been modified or updated through a formal revision process.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b63b0bc8190864d7324d339fb48 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.