Triple
T22780417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peace Preservation Law amendments of 1928 |
E563820
|
entity |
| Predicate | punishmentIncludes |
P149700
|
FINISHED |
| Object | long-term imprisonment |
—
|
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: long-term imprisonment | Statement: [Peace Preservation Law amendments of 1928, punishmentIncludes, long-term imprisonment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: punishmentIncludes Context triple: [Peace Preservation Law amendments of 1928, punishmentIncludes, long-term imprisonment]
-
A.
punishedAmong
Indicates that an entity is punished within a particular group or set of entities, as one among them.
-
B.
punishmentMethod
Indicates the method or means by which a punishment is carried out on an entity.
-
C.
punish
Indicates imposing a penalty or negative consequence on an entity in response to its perceived wrongdoing or rule violation.
-
D.
punishmentDescribedAs
Indicates that one entity characterizes, labels, or portrays a punishment using a particular description or term.
-
E.
punishedBy
Indicates that an entity receives punishment administered by another entity.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2cab0881908df1d0629b43d350 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:28 p.m.