Triple
T2128548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernesto Arturo Miranda |
E46480
|
entity |
| Predicate | retrial |
P18243
|
FINISHED |
| Object | was retried in Arizona state court |
—
|
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: was retried in Arizona state court | Statement: [Ernesto Arturo Miranda, retrial, was retried in Arizona state court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retrial Context triple: [Ernesto Arturo Miranda, retrial, was retried in Arizona state court]
-
A.
reargued
Indicates that an argument, case, or issue was presented and debated again, typically after having been argued previously.
-
B.
trial
chosen
Indicates that an entity is the subject of a legal or formal judicial proceeding to determine guilt, liability, or resolution of a dispute.
-
C.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
D.
reArrested
Indicates that an entity is arrested again after having been previously released or arrested before.
-
E.
reiterates
Indicates that an entity repeats or restates something that was previously expressed, often to emphasize or clarify it.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb7659f48190871cb27faf47e18a |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.