Triple
T18092348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of New Jersey v. Rubin Carter |
E433001
|
entity |
| Predicate | federalCourtHolding |
P50765
|
FINISHED |
| Object | convictions vacated |
—
|
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: convictions vacated | Statement: [State of New Jersey v. Rubin Carter, federalCourtHolding, convictions vacated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: federalCourtHolding Context triple: [State of New Jersey v. Rubin Carter, federalCourtHolding, convictions vacated]
-
A.
judicialFinding
Indicates a formal determination or conclusion reached by a judicial authority regarding facts, law, or liability in a legal matter.
-
B.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
C.
doctrineHeld
Indicates that an agent adheres to, supports, or maintains a particular doctrine or set of principles.
-
D.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
E.
heldByCourt
chosen
Indicates that a particular legal position, opinion, or decision is asserted or determined by a court.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd1972a881908072990de0715547 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.