Triple
T33205603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NADPH |
E850008
|
entity |
| Predicate | hasRedoxState |
P204262
|
FINISHED |
| Object | reduced |
—
|
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: reduced | Statement: [NADPH, hasRedoxState, reduced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRedoxState Context triple: [NADPH, hasRedoxState, reduced]
-
A.
hasTypicalOxidationState
Indicates that an element or species is associated with a commonly observed or characteristic oxidation state under standard or typical conditions.
-
B.
hasOtherPossibleOxidationState
Indicates that an entity, typically a chemical species, can exist in at least one additional oxidation state beyond the one currently specified.
-
C.
hasFormalOxidationStateOfMetal
Indicates that a metal entity is assigned a specific formal oxidation state in a chemical context.
-
D.
redoxProcess
Indicates a process in which one entity undergoes oxidation while another undergoes reduction, involving the transfer of electrons between them.
-
E.
oxidizerState
Indicates the physical or chemical state (e.g., solid, liquid, gas, concentration, or phase condition) in which an oxidizing agent exists during a reaction or process.
- F. None of above. chosen
Provenance (4 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a035ac41d088190b7e76b93c1410090 |
completed | May 12, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_6a035a4f290c8190a0101295a38ae8b8 |
completed | May 12, 2026, 4:50 p.m. |
| PDg | Predicate description generation | batch_6a035ac33bb08190b338ad792ab1b6cd |
completed | May 12, 2026, 4:52 p.m. |
Created at: May 1, 2026, 1:30 a.m.