Triple
T34691660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellis Unit |
E890913
|
entity |
| Predicate | deathRowRelocatedTo |
P182290
|
FINISHED |
| Object | Allan B. Polunsky Unit |
—
|
NE NERFINISHED |
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: Allan B. Polunsky Unit | Statement: [Ellis Unit, deathRowRelocatedTo, Allan B. Polunsky Unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathRowRelocatedTo Context triple: [Ellis Unit, deathRowRelocatedTo, Allan B. Polunsky Unit]
-
A.
deathRowIncarceration
Indicates that an individual is incarcerated in prison under a death sentence, awaiting execution.
-
B.
deathPeninsula
Indicates a relationship where a death occurs on, near, or in association with a specific peninsula.
-
C.
deathPenaltyImposed
Indicates that a legal authority has formally assigned the death penalty as the punishment for an entity.
-
D.
diedInCustodyOf
Indicates that an individual died while under the control, supervision, or physical custody of a specified authority or entity.
-
E.
deathPenaltyImposedFor
Indicates that a death penalty has been officially assigned as the punishment for a particular offense or action.
- F. None of above. chosen
Provenance (4 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 1, 2026, 2:05 a.m.