Triple
T33205604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NADPH |
E850008
|
entity |
| Predicate | isConjugateWith |
P65691
|
FINISHED |
| Object | NADP+ |
—
|
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: NADP+ | Statement: [NADPH, isConjugateWith, NADP+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConjugateWith Context triple: [NADPH, isConjugateWith, NADP+]
-
A.
hasConjugateConcept
Indicates that one concept is the conjugate (e.g., complex, algebraic, or structurally dual counterpart) of another concept within a given formal system.
-
B.
isConjugatedTo
Indicates that two verb forms are related as different inflectional variants of the same verb through conjugation.
-
C.
conjugateTo
Indicates that one entity can be transformed into the other by a specific equivalence operation (such as similarity or group conjugation), so they are equivalent up to that transformation.
-
D.
isInverseOf
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
-
E.
conjugacyProperty
chosen
Indicates that two elements or structures are related by conjugation, sharing the same form up to an inner automorphism or similarity transformation.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:30 a.m.