Triple
T11610042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Blood |
E275359
|
entity |
| Predicate | penaltyImposed |
P3012
|
FINISHED |
| Object | death sentences |
—
|
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 sentences | Statement: [Council of Blood, penaltyImposed, death sentences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyImposed Context triple: [Council of Blood, penaltyImposed, death sentences]
-
A.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
B.
hasPunishment
chosen
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
-
C.
penaltyProvision
Indicates that a rule, contract, or law includes a clause specifying a punishment or sanction for non-compliance or violation.
-
D.
penaltiesAdjustedBy
Indicates that one entity’s penalties are modified, recalculated, or otherwise changed as a result of another entity’s influence or action.
-
E.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a04231d08190b8a07cd977d11ffa |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.