Triple
T26530690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian Jews |
E670811
|
entity |
| Predicate | estimatedHolocaustVictims |
P5134
|
FINISHED |
| Object | hundreds of thousands |
—
|
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: hundreds of thousands | Statement: [Romanian Jews, estimatedHolocaustVictims, hundreds of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedHolocaustVictims Context triple: [Romanian Jews, estimatedHolocaustVictims, hundreds of thousands]
-
A.
numberOfJewsKilled
chosen
Indicates the quantity of Jewish people who were killed in a given event, context, or time period.
-
B.
numberOfGermanVictims
Indicates the quantity of victims who are identified as German in the context of the described event or situation.
-
C.
numberOfJewsDeportedToConcentrationCamps
Indicates the number of Jewish individuals who were forcibly taken and sent to concentration camps.
-
D.
HolocaustImpact
Indicates the effect or consequences that the Holocaust had on individuals, groups, societies, or subsequent events.
-
E.
totalDeathsIncludingPerpetrators
Indicates the total number of deaths resulting from an event, counting both victims and the perpetrators.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:35 a.m.