Triple
T31923705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in the Netherlands |
E815040
|
entity |
| Predicate | deathTollGroup |
P700
|
FINISHED |
| Object | approximately 102000 murdered Dutch Jews |
—
|
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: approximately 102000 murdered Dutch Jews | Statement: [Holocaust in the Netherlands, deathTollGroup, approximately 102000 murdered Dutch Jews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathTollGroup Context triple: [Holocaust in the Netherlands, deathTollGroup, approximately 102000 murdered Dutch Jews]
-
A.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
B.
deathTollEstimate
chosen
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
-
C.
deathTollRanking
Indicates the relative position of an event or entity when ordered by the number of deaths it caused, typically from highest to lowest.
-
D.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
E.
causedFatalities
Indicates that the referenced event or action directly resulted in one or more deaths.
- 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_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 12:03 a.m.