Triple
T35128828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 16 – Motion to Dismiss |
E1014382
|
entity |
| Predicate | effectOfGrant |
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 16 – Motion to Dismiss, effectOfGrant, dismissal of the complaint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfGrant Context triple: [Rule 16 – Motion to Dismiss, effectOfGrant, dismissal of the complaint]
-
A.
grantsStatusEffect
Indicates that one entity applies or bestows a specific status effect onto another entity.
-
B.
effectOfDesignation
Indicates the causal impact or consequences that a particular designation or assigned status has on something.
-
C.
affectsBenefit
Indicates that one entity has an influence on, modifies, or determines the benefit or advantage received by another entity.
-
D.
aimedToGrant
Indicates an intention or effort to provide or confer something (such as a right, benefit, or permission) to a recipient.
-
E.
grantsAdvantage
Indicates that one entity provides another entity with a benefit, edge, or favorable position in a given context.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: May 3, 2026, 4:02 p.m.