Triple
T473351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Constitution |
E9006
|
entity |
| Predicate | currentVersionAdoptedOn |
P3399
|
FINISHED |
| Object | 1876-02-15 |
—
|
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: 1876-02-15 | Statement: [Texas Constitution, currentVersionAdoptedOn, 1876-02-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVersionAdoptedOn Context triple: [Texas Constitution, currentVersionAdoptedOn, 1876-02-15]
-
A.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
B.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
-
C.
previousVersionLocationOfAdoption
Indicates that one entity is the location where an earlier or prior version of another entity was adopted.
-
D.
adoptedAt
Indicates the time or date at which an adoption event took place.
-
E.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0208c788190a96cdabcf593fda7 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.