Triple
T2253347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simele massacre |
E49664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Iraq |
C1824
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: event in Iraq Context triple: [Simele massacre, instanceOf, event in Iraq]
-
A.
Iraq–United Nations relations event
An Iraq–United Nations relations event is an occurrence or series of actions involving diplomatic, political, humanitarian, or security interactions between Iraq and the United Nations that significantly affects their bilateral relationship.
-
B.
subdivision of Iraq
A subdivision of Iraq is an administrative region within the country, such as a governorate, district, or subdistrict, established for local governance and organizational purposes.
-
C.
event in the Troubles
An event in the Troubles is a specific incident—such as a violent attack, political action, protest, or security operation—that occurred during the Northern Ireland conflict between the late 1960s and 1998 and had social, political, or historical significance.
-
D.
event in the Russo-Ukrainian War
An event in the Russo-Ukrainian War is a specific, temporally and geographically bounded occurrence—such as a battle, diplomatic action, territorial change, or significant incident—that affects the course, perception, or outcomes of the conflict.
-
E.
event
chosen
An event is a distinct occurrence or happening, often bounded in time and space, that involves one or more participants and may trigger changes in state or behavior within a system.
- F. None of above.
Provenance (1 batch)
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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:47 p.m.