Triple
T31923721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust in the Netherlands |
E815040
|
entity |
| Predicate | resistanceContext |
P43585
|
FINISHED |
| Object | Dutch resistance |
—
|
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: Dutch resistance | Statement: [Holocaust in the Netherlands, resistanceContext, Dutch resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resistanceContext Context triple: [Holocaust in the Netherlands, resistanceContext, Dutch resistance]
-
A.
typeOfResistance
chosen
Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
-
B.
unitOfResistance
Indicates that one entity represents a unit used to measure electrical resistance of another entity.
-
C.
resistedIn
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
D.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
E.
methodOfResistance
Indicates a way or technique by which resistance is carried out or expressed.
- 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_69f6b1fa05a081909ba84d0efc314ec4 |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca7081881909e96a8b05ec086bb |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:03 a.m.