Triple
T30718335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumgait pogrom |
E782083
|
entity |
| Predicate | victimProperty |
P171092
|
FINISHED |
| Object | Armenian homes and businesses |
—
|
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: Armenian homes and businesses | Statement: [Sumgait pogrom, victimProperty, Armenian homes and businesses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimProperty Context triple: [Sumgait pogrom, victimProperty, Armenian homes and businesses]
-
A.
victimWealthStatus
Indicates the economic or financial status of the victim in relation to the event or situation being described.
-
B.
victimParty
Indicates that one party is the victim or harmed side in an event, action, or situation involving another party.
-
C.
victimCategory
Indicates the classification or type of victim associated with an event, action, or harmful outcome.
-
D.
victimOrigin
Indicates that an entity is the place, group, or context from which a victim originates or is drawn.
-
E.
victimHouse
Indicates that a particular house is the residence or location associated with the victim in an incident or event.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:36 p.m.