Triple
T35974101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farhud |
E1040365
|
entity |
| Predicate | hasPropertyDestruction |
P207119
|
FINISHED |
| Object | synagogues damaged |
—
|
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: synagogues damaged | Statement: [Farhud, hasPropertyDestruction, synagogues damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPropertyDestruction Context triple: [Farhud, hasPropertyDestruction, synagogues damaged]
-
A.
possiblyDestroyedIn
Indicates that an entity may have been destroyed during or as a result of a specified event or situation.
-
B.
hasOnScreenDestruction
Indicates that something is depicted being damaged, ruined, or destroyed within the visible content (e.g., on screen or in the scene).
-
C.
canDestroy
Indicates that one entity has the ability or power to destroy another entity.
-
D.
destroyedAfter
Indicates that one entity is destroyed at a point in time that occurs after the destruction of another entity.
-
E.
afterDestruction
Indicates that one event, state, or condition occurs subsequent to and as a result of a prior act of destruction.
- F. None of above. chosen
Provenance (4 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.