Triple
T32851580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juror 5 |
E840265
|
entity |
| Predicate | supportsJuror |
—
|
GENERATED |
| Object | Juror 8 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsJuror Context triple: [Juror 5, supportsJuror, Juror 8]
-
A.
hasJuror
Indicates that a person or legal body is assigned or associated with a specific juror in a judicial context.
-
B.
usesJury
Indicates that a legal proceeding or decision-making process is conducted with the participation of a jury.
-
C.
hasJurors
Indicates that one entity serves as or includes jurors in relation to another entity, typically in the context of a legal case or proceeding.
-
D.
supportsProsecutionIn
Indicates that an entity provides assistance or backing to the prosecution side within a specified legal case or jurisdiction.
-
E.
supportsJurisdiction
Indicates that one jurisdiction provides backing, authority, or legal support for the actions, decisions, or existence of another jurisdiction.
- F. None of above. chosen
Provenance (1 batch)
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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:17 a.m.