Triple
T18866262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bubanj Memorial Park |
E461444
|
entity |
| Predicate | hasMassGrave |
P123119
|
FINISHED |
| Object | site of execution of thousands of civilians |
—
|
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: site of execution of thousands of civilians | Statement: [Bubanj Memorial Park, hasMassGrave, site of execution of thousands of civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassGrave Context triple: [Bubanj Memorial Park, hasMassGrave, site of execution of thousands of civilians]
-
A.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
B.
hasMassGraves
chosen
Indicates that a location or entity contains or is associated with one or more mass graves.
-
C.
numberOfMassGraves
Indicates the quantity of mass graves associated with or present at a given entity or location.
-
D.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
E.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a5074481908941fcbb3b3eefa2 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.