Triple
T35129477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 33 – Demurrer to Evidence |
E1014398
|
entity |
| Predicate | effectIfDenied |
P167278
|
FINISHED |
| Object | defendant may present evidence |
—
|
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: defendant may present evidence | Statement: [Rule 33 – Demurrer to Evidence, effectIfDenied, defendant may present evidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectIfDenied Context triple: [Rule 33 – Demurrer to Evidence, effectIfDenied, defendant may present evidence]
-
A.
resultOfDenial
chosen
Indicates that something occurs or exists as a consequence of a prior denial event or refusal.
-
B.
deniedAs
Indicates that one entity has refused, rejected, or not granted a request, claim, or association involving another entity.
-
C.
isDeniedBy
Indicates that a request, claim, or action directed at an entity is explicitly refused or rejected by another entity.
-
D.
deniedTo
Indicates that access, permission, or a requested benefit is explicitly refused or withheld from a particular entity.
-
E.
typicallyDenies
Indicates that an entity, in most usual or common circumstances, refuses, rejects, or does not grant something to another 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:02 p.m.