Triple
T6393677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 35 |
E143888
|
entity |
| Predicate | doesNotAuthorize |
P49355
|
FINISHED |
| Object | de novo resentencing |
—
|
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: de novo resentencing | Statement: [Rule 35, doesNotAuthorize, de novo resentencing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotAuthorize Context triple: [Rule 35, doesNotAuthorize, de novo resentencing]
-
A.
doesNotAllow
Indicates that one entity prevents, forbids, or does not permit another entity from performing a specific action or being in a certain state.
-
B.
notAuthorizedFor
chosen
Indicates that an entity lacks the required permission or authority to perform a specific action or access a particular resource.
-
C.
doesNotAccept
Indicates that one entity refuses, rejects, or is not configured to receive or allow something from another entity.
-
D.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
canAuthorize
Indicates that one entity has the power or permission to grant approval or official permission for another entity to perform an action or access a resource.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06881313481908e9082ffe57f29b6 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.