Triple
T24006181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buchach |
E594391
|
entity |
| Predicate | sufferedDuring |
P91920
|
FINISHED |
| Object | Holocaust |
—
|
NE NERFINISHED |
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: Holocaust | Statement: [Buchach, sufferedDuring, Holocaust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sufferedDuring Context triple: [Buchach, sufferedDuring, Holocaust]
-
A.
sufferedCondition
chosen
Indicates that an entity experienced or was afflicted by a particular condition, typically adverse or harmful, at some point in time.
-
B.
sufferedDamageTo
Indicates that one entity has experienced harm, loss, or deterioration affecting another entity or one of its parts.
-
C.
sufferedEventDate
Indicates the specific date on which an entity experienced or was affected by a particular event.
-
D.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
E.
burnedDuring
Indicates that one event, object, or process was actively burning or being consumed by fire during the time span of another specified event or interval.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d4693a8c8190af2960c5832093f1 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.