Triple
T26143491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potočari |
E659586
|
entity |
| Predicate | hasVictimsBuriedFrom |
P45931
|
FINISHED |
| Object | Bratunac area |
—
|
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: Bratunac area | Statement: [Potočari, hasVictimsBuriedFrom, Bratunac area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVictimsBuriedFrom Context triple: [Potočari, hasVictimsBuriedFrom, Bratunac area]
-
A.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
B.
numberOfVictimsInMassGraves
Indicates the count of individuals who were killed and buried together in mass graves associated with a particular event or context.
-
C.
hasBurialsFrom
chosen
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of another entity.
-
E.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 26, 2026, 8:21 p.m.