Triple
T7397456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scopes v. State |
E170656
|
entity |
| Predicate | fineImposedByTrialCourt |
P11395
|
FINISHED |
| Object | 100 US dollars |
—
|
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: 100 US dollars | Statement: [Scopes v. State, fineImposedByTrialCourt, 100 US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fineImposedByTrialCourt Context triple: [Scopes v. State, fineImposedByTrialCourt, 100 US dollars]
-
A.
trialCourt
Indicates that a legal matter, decision, or proceeding is associated with, handled by, or occurring in a court of first instance (the trial-level court).
-
B.
trialHeldIn
Indicates that a legal trial took place or was conducted within a specified location or jurisdiction.
-
C.
courtOrdered
chosen
Indicates that an action, condition, or relationship exists because it has been formally mandated or imposed by a court order.
-
D.
heldCourtUnder
Indicates that one authority conducted judicial or ceremonial court proceedings under the jurisdiction, auspices, or authority of another.
-
E.
facedTribunal
Indicates that an entity has been brought before and judged by a formal tribunal or judicial body.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24abcd08190b8428fa22b2fbd4f |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.