Triple
T22422212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First they came... |
E554274
|
entity |
| Predicate | memorialUse |
P25987
|
FINISHED |
| Object | inscriptions at Holocaust memorials |
—
|
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: inscriptions at Holocaust memorials | Statement: [First they came..., memorialUse, inscriptions at Holocaust memorials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memorialUse Context triple: [First they came..., memorialUse, inscriptions at Holocaust memorials]
-
A.
commemorationUse
Indicates the use of something specifically for commemorating or honoring an event, person, or occasion.
-
B.
memorialization
chosen
Indicates the act of preserving the memory or honoring the legacy of someone or something, often through a dedicated object, event, or practice.
-
C.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember another entity.
-
D.
memorialType
Indicates the specific kind or category of memorial associated with an entity (e.g., plaque, statue, monument).
-
E.
memorialScope
Indicates the extent or boundaries of what is commemorated or covered by a memorial.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2a1a3c8190a649ee4df2429e69 |
completed | April 29, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:47 p.m.