Triple
T33148476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sardasht |
E848369
|
entity |
| Predicate | chemicalAgentUsed |
P160673
|
FINISHED |
| Object | sulfur mustard |
—
|
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: sulfur mustard | Statement: [Sardasht, chemicalAgentUsed, sulfur mustard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chemicalAgentUsed Context triple: [Sardasht, chemicalAgentUsed, sulfur mustard]
-
A.
chemicalWeaponsUsedIn
Indicates that chemical weapons were employed during a specific event, conflict, or incident in a given location or context.
-
B.
destroyedChemicalAgent
Indicates that an entity has rendered a chemical agent unusable or eliminated it, typically through neutralization, dismantling, or disposal.
-
C.
chemicalWeaponUseContext
Indicates the situational circumstances or conditions under which a chemical weapon is used.
-
D.
combatantUsedPoisonGas
chosen
Indicates that a combatant employed poison gas as a method or means of attack in a conflict or engagement.
-
E.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:28 a.m.