Triple
T32389038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Vane |
E827615
|
entity |
| Predicate | deathPenaltyType |
P179844
|
FINISHED |
| Object | capital punishment |
—
|
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: capital punishment | Statement: [Charles Vane, deathPenaltyType, capital punishment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathPenaltyType Context triple: [Charles Vane, deathPenaltyType, capital punishment]
-
A.
deathPenaltyImposedFor
Indicates that a death penalty has been officially assigned as the punishment for a particular offense or action.
-
B.
deathPenaltyImposed
Indicates that a legal authority has formally assigned the death penalty as the punishment for an entity.
-
C.
deathPenaltySought
Indicates that legal authorities are actively pursuing the imposition of the death penalty as a possible or intended punishment in a given case.
-
D.
deathPenaltyJurisdiction
Indicates that a given jurisdiction legally authorizes, applies, or recognizes the death penalty as a form of criminal punishment.
-
E.
deathRowIncarceration
Indicates that an individual is incarcerated in prison under a death sentence, awaiting execution.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 12:52 a.m.