Triple
T14311969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 403 |
E354853
|
entity |
| Predicate | discretion |
P51714
|
FINISHED |
| Object | trial court discretion |
—
|
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: trial court discretion | Statement: [Rule 403, discretion, trial court discretion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discretion Context triple: [Rule 403, discretion, trial court discretion]
-
A.
isDiscretionary
chosen
Indicates that the action or decision is optional and left to personal or organizational judgment rather than being mandatory or automatic.
-
B.
decisiveness
Indicates the degree to which an entity consistently makes timely, firm choices without excessive hesitation or reversal.
-
C.
meetsAtDiscretionOf
Indicates that one entity meets another at times or under conditions determined solely by the discretion or choice of a specified party.
-
D.
chairDiscretion
Indicates that something occurs, is decided, or is allowed based on the judgment or discretionary authority of the chairperson or presiding officer.
-
E.
decisive
Indicates that one entity makes a conclusive choice or determination that resolves a situation or outcome between entities.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b386d0819087d14f3ce84a1997 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.