Triple
T2191007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NDH |
E49859
|
entity |
| Predicate | warCrimePolicy |
P22567
|
FINISHED |
| Object | genocide of Serbs |
—
|
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 of Serbs | Statement: [NDH, warCrimePolicy, genocide of Serbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warCrimePolicy Context triple: [NDH, warCrimePolicy, genocide of Serbs]
-
A.
warCrimesContext
chosen
Indicates a context in which actions or events are associated with the commission, investigation, or adjudication of war crimes.
-
B.
politicalConflict
Indicates a relationship where entities are engaged in opposing political positions, struggles, or disputes, often involving competition for power, influence, or policy outcomes.
-
C.
genocide
Indicates the deliberate and systematic destruction, in whole or in part, of a national, ethnic, racial, or religious group.
-
D.
militaryPolicy
Indicates a relationship where an entity defines, adopts, or is governed by rules, strategies, or doctrines concerning military organization, operations, or conduct.
-
E.
opposedWar
Indicates that an entity actively resisted, disagreed with, or worked against a particular war or military conflict.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf3f5e008190beda3ce5d77209e0 |
completed | March 7, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.