Triple
T30199440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanging Judge |
E767731
|
entity |
| Predicate | associatedWithPunishmentType |
P3012
|
FINISHED |
| Object | hanging |
—
|
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: hanging | Statement: [Hanging Judge, associatedWithPunishmentType, hanging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPunishmentType Context triple: [Hanging Judge, associatedWithPunishmentType, hanging]
-
A.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
B.
sharesPunishmentWith
Indicates that two or more entities receive or experience the same punishment or penalty together.
-
C.
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.
-
D.
punishedAmong
Indicates that an entity is punished within a particular group or set of entities, as one among them.
-
E.
punishmentIncludes
Indicates that a specified punishment encompasses or contains another specified punitive measure as one of its components.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:30 p.m.