Triple
T15478566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAD+ |
E376853
|
entity |
| Predicate | redoxPairWith |
P118409
|
FINISHED |
| Object | NADH |
—
|
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: NADH | Statement: [NAD+, redoxPairWith, NADH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redoxPairWith Context triple: [NAD+, redoxPairWith, NADH]
-
A.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
B.
commonPair
Indicates that two entities commonly occur together or are frequently associated as a pair in some shared context.
-
C.
isPairOf
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
D.
pairedSingleWith
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
E.
associatedWithRight
Indicates a relationship in which an entity is connected to, linked with, or related to something characterized as "right" (such as a right-hand side, a legal right, or a correct option), depending on the domain context.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8a77a081909f12f13660452f4a |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:34 a.m.