Triple
T28806369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bogdanovka massacre |
E727384
|
entity |
| Predicate | usedSiteAs |
P62923
|
FINISHED |
| Object | concentration camp |
—
|
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: concentration camp | Statement: [Bogdanovka massacre, usedSiteAs, concentration camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSiteAs Context triple: [Bogdanovka massacre, usedSiteAs, concentration camp]
-
A.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
-
B.
hasSiteUse
chosen
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
C.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
D.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
currentSiteUse
Indicates how a site is presently being used or the function it currently serves.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:29 a.m.