Triple
T32696975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juror 2 |
E836035
|
entity |
| Predicate | supportsVerdict |
P146791
|
FINISHED |
| Object | guilty (initially) |
—
|
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: guilty (initially) | Statement: [Juror 2, supportsVerdict, guilty (initially)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsVerdict Context triple: [Juror 2, supportsVerdict, guilty (initially)]
-
A.
supportsDecisionOf
chosen
Indicates that one entity endorses, backs, or agrees with the decision made by another entity.
-
B.
supportsConclusionOf
Indicates that one entity provides justification, evidence, or reasoning that backs up or helps establish the conclusion represented by another entity.
-
C.
supportsProsecutionIn
Indicates that an entity provides assistance or backing to the prosecution side within a specified legal case or jurisdiction.
-
D.
supportsOutcome
Indicates that one entity contributes to enabling, sustaining, or improving the achievement of a particular outcome associated with another entity.
-
E.
verdict
Indicates the formal decision or judgment reached and declared at the conclusion of a legal or evaluative process.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:10 a.m.