Triple
T4673235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas abortion laws |
E103613
|
entity |
| Predicate | criminalPenaltyAppliesTo |
P18713
|
FINISHED |
| Object | abortion providers |
—
|
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: abortion providers | Statement: [Texas abortion laws, criminalPenaltyAppliesTo, abortion providers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criminalPenaltyAppliesTo Context triple: [Texas abortion laws, criminalPenaltyAppliesTo, abortion providers]
-
A.
isCriminalizedIn
chosen
Indicates that a specific behavior, action, or condition is prohibited and subject to legal penalties within a particular jurisdiction or legal system.
-
B.
haveCriminalLaw
Indicates that an entity possesses, applies, or is governed by a system or body of criminal law.
-
C.
convictedOf
Indicates that a person or entity has been found guilty of committing a specified offense or crime through a formal legal process.
-
D.
criminalStatus
Indicates the legal condition of an entity with respect to criminal law, such as whether they are accused, convicted, or cleared of a crime.
-
E.
crimeType
Indicates the specific category or nature of the crime associated with an event or 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_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.