Triple
T31668038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | grave breaches of the Geneva Conventions |
E808187
|
entity |
| Predicate | punishableBy |
P3012
|
FINISHED |
| Object | criminal prosecution |
—
|
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: criminal prosecution | Statement: [grave breaches of the Geneva Conventions, punishableBy, criminal prosecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: punishableBy Context triple: [grave breaches of the Geneva Conventions, punishableBy, criminal prosecution]
-
A.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
B.
punishedAmong
Indicates that an entity is punished within a particular group or set of entities, as one among them.
-
C.
punishmentIncludes
Indicates that a specified punishment encompasses or contains another specified punitive measure as one of its components.
-
D.
punish
Indicates imposing a penalty or negative consequence on an entity in response to its perceived wrongdoing or rule violation.
-
E.
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.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11 p.m.