Triple
T8278400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zinin reduction |
E193604
|
entity |
| Predicate | commonReagent |
P79100
|
FINISHED |
| Object | ammonium sulfide |
—
|
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: ammonium sulfide | Statement: [Zinin reduction, commonReagent, ammonium sulfide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonReagent Context triple: [Zinin reduction, commonReagent, ammonium sulfide]
-
A.
commonChemistry
Indicates that two entities share similar or related chemical properties, composition, or behavior.
-
B.
chemicallyRelatedTo
Indicates a relationship where two entities are connected through a chemical association, such as sharing structural features, participating in related reactions, or being derivable from one another chemically.
-
C.
chemicalComponent
Indicates that one entity is a constituent chemical part or ingredient of another entity.
-
D.
reactant
chosen
Indicates that an entity participates as a starting material or input substance in a chemical or reactive process.
-
E.
typicalSolvent
Indicates that one entity is commonly or characteristically used as a solvent for the other entity.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ebb6b88190bc777b8bd72fcdbc |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.