Triple
T29302292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halabja Memorial Day |
E742990
|
entity |
| Predicate | commemorativeEventFor |
P27243
|
FINISHED |
| Object | Halabja |
—
|
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: Halabja | Statement: [Halabja Memorial Day, commemorativeEventFor, Halabja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemorativeEventFor Context triple: [Halabja Memorial Day, commemorativeEventFor, Halabja]
-
A.
commemorativeEvent
chosen
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
-
B.
commemoratesEventWith
Indicates that one entity serves as a memorial or tribute to a specific event, marking or honoring its occurrence.
-
C.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
-
D.
commemoratesEventDescribedIn
Indicates that something serves to honor or remember an event that is described in a particular source or representation.
-
E.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 1:10 p.m.