Triple
T19866953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izium |
E477414
|
entity |
| Predicate | massGraveApproxBodies |
P137629
|
FINISHED |
| Object | over 400 bodies |
—
|
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: over 400 bodies | Statement: [Izium, massGraveApproxBodies, over 400 bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massGraveApproxBodies Context triple: [Izium, massGraveApproxBodies, over 400 bodies]
-
A.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
B.
hasMassGraves
Indicates that a location or entity contains or is associated with one or more mass graves.
-
C.
massGravesDiscovered
Indicates that previously unknown burial sites containing multiple bodies have been found.
-
D.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
E.
bodiesExhumed
Indicates that previously buried bodies have been dug up and removed from their place of interment.
- F. None of above. chosen
Provenance (4 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6589f9654819080597a4f7c52d64c |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.