Triple
T26602904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ypres 1915 |
E667683
|
entity |
| Predicate | poisonGasType |
P8036
|
FINISHED |
| Object | chlorine gas |
—
|
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: chlorine gas | Statement: [Ypres 1915, poisonGasType, chlorine gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poisonGasType Context triple: [Ypres 1915, poisonGasType, chlorine gas]
-
A.
poisonUsed
Indicates that one entity employed poison as a means to harm, kill, or incapacitate another entity.
-
B.
toxinType
chosen
Indicates the specific kind or category of toxin associated with an entity.
-
C.
hasToxicSap
Indicates that an entity produces or contains sap that is harmful or poisonous to other organisms.
-
D.
destroyedChemicalAgent
Indicates that an entity has rendered a chemical agent unusable or eliminated it, typically through neutralization, dismantling, or disposal.
-
E.
toxicTo
Indicates that one entity causes harm, poisoning, or adverse effects to another when exposed or applied.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6157198fc819083151a884187abae |
completed | May 2, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:13 a.m.