Triple
T4267230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations crime suppression conventions |
E96854
|
entity |
| Predicate | includesCrimeType |
P7957
|
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: [United Nations crime suppression conventions, includesCrimeType, genocide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCrimeType Context triple: [United Nations crime suppression conventions, includesCrimeType, genocide]
-
A.
crimeType
chosen
Indicates the specific category or nature of the crime associated with an event or entity.
-
B.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
-
C.
haveCriminalLaw
Indicates that an entity possesses, applies, or is governed by a system or body of criminal law.
-
D.
recognitionOfCrimes
Indicates the formal acknowledgment or identification that certain actions or events constitute crimes under a legal or normative framework.
-
E.
crimeListedInArticleIII
Indicates that a particular crime is one of the offenses expressly mentioned in Article III of the relevant constitution or legal document.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fce710481909d90ed4a3d150fde |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.