Triple
T18845568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate Bill 8 (2021) |
E460903
|
entity |
| Predicate | lacksExceptionFor |
P19461
|
FINISHED |
| Object | rape |
—
|
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: rape | Statement: [Senate Bill 8 (2021), lacksExceptionFor, rape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lacksExceptionFor Context triple: [Senate Bill 8 (2021), lacksExceptionFor, rape]
-
A.
doesNotProvideExceptionFor
chosen
Indicates that one party or rule fails to grant an exemption, special case, or exclusion to another party or situation.
-
B.
hasExceptionFor
Indicates that a general rule, condition, or behavior does not apply in a particular case or under specific circumstances.
-
C.
hasExceptionConstruct
Indicates that a construct or element is associated with, or defined by, a specific exception-handling construct (such as a try-catch or similar exception mechanism).
-
D.
hasException
Indicates that a general rule, process, or condition does not apply in a particular case due to a specified exception.
-
E.
failsInGeneralFor
Indicates that an action, method, or approach does not succeed under typical or broad conditions, rather than only in specific edge cases.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ee96988190bf247b986777945c |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.