Triple
T10883338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovak Jews |
E256977
|
entity |
| Predicate | populationBeforeHolocaust |
P40411
|
FINISHED |
| Object | tens 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: tens of thousands | Statement: [Slovak Jews, populationBeforeHolocaust, tens of thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationBeforeHolocaust Context triple: [Slovak Jews, populationBeforeHolocaust, tens of thousands]
-
A.
hadSignificantJewishPopulationBeforeWorldWarII
chosen
Indicates that the subject place or region had a notably large or influential Jewish community prior to the outbreak of World War II.
-
B.
mainTerritoryBeforeHolocaust
Indicates the primary geographic area in which an entity was located or based prior to the Holocaust.
-
C.
numberOfJewsKilled
Indicates the quantity of Jewish people who were killed in a given event, context, or time period.
-
D.
HolocaustImpact
Indicates the effect or consequences that the Holocaust had on individuals, groups, societies, or subsequent events.
-
E.
numberOfJewsDeportedToConcentrationCamps
Indicates the number of Jewish individuals who were forcibly taken and sent to concentration camps.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751db24208190b3a7ed7eea118522 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.