Triple
T32152710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Kirkland Batson |
E821200
|
entity |
| Predicate | hasRoleInCase |
P16985
|
FINISHED |
| Object | defendant in Batson v. Kentucky |
—
|
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: defendant in Batson v. Kentucky | Statement: [James Kirkland Batson, hasRoleInCase, defendant in Batson v. Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInCase Context triple: [James Kirkland Batson, hasRoleInCase, defendant in Batson v. Kentucky]
-
A.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
C.
legalCaseRole
chosen
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
D.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
-
E.
hasJuryRole
Indicates that an entity serves in a jury capacity or holds a specific role within a jury in relation to another entity or proceeding.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 1, 2026, 12:32 a.m.