Triple
T8513809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flossenbürg concentration camp |
E201519
|
entity |
| Predicate | victimEstimate |
P74879
|
FINISHED |
| Object | 30000 |
—
|
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: 30000 | Statement: [Flossenbürg concentration camp, victimEstimate, 30000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimEstimate Context triple: [Flossenbürg concentration camp, victimEstimate, 30000]
-
A.
estimatedVictimsUnderAuthority
Indicates that a specified authority is estimated to have a certain number of victims under its control, influence, or jurisdiction.
-
B.
numberOfVictimsClaimed
chosen
Indicates the reported count of victims associated with a particular event, incident, or action.
-
C.
mainVictims
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
-
D.
numberOfSuspectedVictims
Indicates the count of individuals believed or alleged to be victims in a particular incident, case, or context.
-
E.
numberOfVictimsKilled
Indicates the count of victims who were killed as a result of the referenced event or action.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe60cdfcc819081a9be1229378ba0 |
completed | March 31, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:15 p.m.