Triple
T30801499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penal Code (1810) |
E784380
|
entity |
| Predicate | establishesPenaltyType |
P166927
|
FINISHED |
| Object | death penalty |
—
|
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: death penalty | Statement: [Penal Code (1810), establishesPenaltyType, death penalty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesPenaltyType Context triple: [Penal Code (1810), establishesPenaltyType, death penalty]
-
A.
penaltyTypes
chosen
Indicates the kinds or categories of penalties that are associated with or applied to an entity or action.
-
B.
penaltyAppliesTo
Indicates that a specific penalty is imposed on, or is relevant to, a particular entity or situation.
-
C.
penaltyProvision
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
D.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
-
E.
penaltyRules
Indicates the rules or conditions under which penalties are defined, applied, or enforced in a given context.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 8:42 p.m.