Triple
T4673231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas abortion laws |
E103613
|
entity |
| Predicate | triggerLawEffectiveDate |
P1260
|
FINISHED |
| Object | August 25, 2022 |
—
|
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: August 25, 2022 | Statement: [Texas abortion laws, triggerLawEffectiveDate, August 25, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggerLawEffectiveDate Context triple: [Texas abortion laws, triggerLawEffectiveDate, August 25, 2022]
-
A.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
B.
dateEnacted
chosen
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
C.
legalDefinitionCameIntoForce
Indicates that a particular legal definition officially became valid and enforceable from a specified point in time.
-
D.
hasLegalEffectToday
Indicates that a legal rule, document, or status is currently in force and produces legal consequences as of today.
-
E.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.