Triple
T17570218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article III of the Genocide Convention |
E427915
|
entity |
| Predicate | definesAsPunishable |
P26615
|
FINISHED |
| Object | genocide |
—
|
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: genocide | Statement: [Article III of the Genocide Convention, definesAsPunishable, genocide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAsPunishable Context triple: [Article III of the Genocide Convention, definesAsPunishable, genocide]
-
A.
definesOffence
chosen
Indicates that one entity specifies or establishes the nature, elements, or scope of an offence associated with another entity.
-
B.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
C.
consideredCriminalBy
Indicates that one party regards or classifies another party as a criminal according to its own laws, rules, or judgments.
-
D.
authorizesPunishment
Indicates that one entity grants permission or legal authority for another entity to impose a punishment.
-
E.
isCriminalizedIn
Indicates that a specific behavior, action, or condition is prohibited and subject to legal penalties within a particular jurisdiction or legal system.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592fe8408190bd8fed1920ab3601 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.