Triple
T35129475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 33 – Demurrer to Evidence |
E1014398
|
entity |
| Predicate | effectIfGranted |
P193679
|
FINISHED |
| Object | dismissal of the complaint |
—
|
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: dismissal of the complaint | Statement: [Rule 33 – Demurrer to Evidence, effectIfGranted, dismissal of the complaint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectIfGranted Context triple: [Rule 33 – Demurrer to Evidence, effectIfGranted, dismissal of the complaint]
-
A.
conditionalEffect
Indicates that one event, state, or action occurs or holds only if a specified condition is met.
-
B.
effectOfGrant
chosen
Indicates the outcome, impact, or change that results from a particular grant being given.
-
C.
grantsStatusEffect
Indicates that one entity applies or bestows a specific status effect onto another entity.
-
D.
believedToGrant
Indicates that something is thought or assumed to provide, confer, or bestow a particular benefit, quality, or effect.
-
E.
grantedPower
Indicates that one entity has conferred authority, control, or a specific capability 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_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:02 p.m.