Triple
T31923706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in the Netherlands |
E815040
|
entity |
| Predicate | deathRate |
P4715
|
FINISHED |
| Object | about 75 percent of Dutch Jews killed |
—
|
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: about 75 percent of Dutch Jews killed | Statement: [Holocaust in the Netherlands, deathRate, about 75 percent of Dutch Jews killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathRate Context triple: [Holocaust in the Netherlands, deathRate, about 75 percent of Dutch Jews killed]
-
A.
mortalityRate
chosen
Indicates the proportion of individuals in a defined population that die within a specified time period.
-
B.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
C.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
D.
caseFatalityRate
Indicates the proportion of deaths among all identified cases of a particular disease or condition within a specified period.
-
E.
deathTollEstimate
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 12:03 a.m.