Triple
T28572715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bechamp reduction |
E723154
|
entity |
| Predicate | reductant |
P79100
|
FINISHED |
| Object | metallic iron |
—
|
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: metallic iron | Statement: [Bechamp reduction, reductant, metallic iron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reductant Context triple: [Bechamp reduction, reductant, metallic iron]
-
A.
reduction
Indicates a relationship where something is decreased in amount, size, intensity, or degree compared to a prior state or reference.
-
B.
reactant
chosen
Indicates that an entity participates as a starting material or input substance in a chemical or reactive process.
-
C.
reduces
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
D.
oxidizer
Indicates a relationship where one entity acts as an oxidizing agent that accepts electrons from, or promotes the oxidation of, another entity in a chemical process.
-
E.
reductionFrom
Indicates that one entity is derived by simplifying, decreasing, or transforming another entity, typically resulting in a smaller, less complex, or less resource-intensive form.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:10 a.m.