Triple
T12069038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson v. Zerbst |
E287372
|
entity |
| Predicate | appliesToDefendants |
P41330
|
FINISHED |
| Object | indigent defendants |
—
|
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: indigent defendants | Statement: [Johnson v. Zerbst, appliesToDefendants, indigent defendants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToDefendants Context triple: [Johnson v. Zerbst, appliesToDefendants, indigent defendants]
-
A.
hasDefendants
Indicates that one or more entities serve as defendants in relation to a particular legal case or proceeding.
-
B.
hasMainDefendant
Indicates that a legal case or proceeding identifies a specific individual or entity as its primary defendant.
-
C.
typicalDefendants
chosen
Indicates that the referenced entities are the ones most commonly or characteristically serving as defendants in the relevant legal context.
-
D.
defendant
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
E.
coDefendant
Indicates that two or more parties are jointly named and involved as defendants in the same legal case 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.