Triple
T14607700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halabja |
E342873
|
entity |
| Predicate | attackLegacy |
P85993
|
FINISHED |
| Object | symbol of Kurdish suffering under Saddam Hussein |
—
|
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: symbol of Kurdish suffering under Saddam Hussein | Statement: [Halabja, attackLegacy, symbol of Kurdish suffering under Saddam Hussein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackLegacy Context triple: [Halabja, attackLegacy, symbol of Kurdish suffering under Saddam Hussein]
-
A.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attacks
Indicates that one entity initiates an aggressive or harmful action directed toward another entity.
-
C.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
-
D.
attackContext
chosen
Indicates the situational circumstances, conditions, or factors surrounding an attack event or action.
-
E.
attacksIf
Indicates that one entity initiates or carries out an attack on another entity when certain conditions are met.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44d327c8190a8d20568429d0f80 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.