Triple
T35650919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evidence Code § 1101 |
E1030144
|
entity |
| Predicate | purposeOfProhibition |
P183576
|
FINISHED |
| Object | to prevent propensity reasoning |
—
|
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: to prevent propensity reasoning | Statement: [Evidence Code § 1101, purposeOfProhibition, to prevent propensity reasoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfProhibition Context triple: [Evidence Code § 1101, purposeOfProhibition, to prevent propensity reasoning]
-
A.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
B.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
restraintPurpose
Indicates that one entity is used to restrain another entity for a specific purpose or intended outcome.
-
D.
isOftenProhibitedAt
Indicates that something is frequently not allowed or banned in a particular place, context, or situation.
-
E.
reasonForBan
Indicates the justification or cause that led to an entity being banned.
- F. None of above. chosen
Provenance (4 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.