Triple
T15478616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAD+ |
E376853
|
entity |
| Predicate | isConvertedBy |
P23777
|
FINISHED |
| Object | dehydrogenase-catalyzed reactions |
—
|
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: dehydrogenase-catalyzed reactions | Statement: [NAD+, isConvertedBy, dehydrogenase-catalyzed reactions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConvertedBy Context triple: [NAD+, isConvertedBy, dehydrogenase-catalyzed reactions]
-
A.
convertedBy
chosen
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
B.
convertsTo
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
-
C.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
-
D.
someConvertedTo
Indicates that a portion of one entity has been transformed or changed into another entity.
-
E.
involvesConversionFrom
Indicates that one entity participates in or requires a transformation or change from another entity as its source or starting point.
- 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_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. |
Created at: April 10, 2026, 3:34 a.m.