Triple
T15478622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAD+ |
E376853
|
entity |
| Predicate | hasHighRatioTo |
P16308
|
FINISHED |
| Object | NADH in cytosol |
—
|
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 in cytosol | Statement: [NAD+, hasHighRatioTo, NADH in cytosol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighRatioTo Context triple: [NAD+, hasHighRatioTo, NADH in cytosol]
-
A.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
B.
hasHighDensityOf
Indicates that one entity contains or exhibits a large concentration or amount of another entity within a given area, volume, or context.
-
C.
hasHighPropertyValues
Indicates that the associated entity possesses property values that are above a defined or typical threshold.
-
D.
hasHighPerUnitValueAgainst
Indicates that one entity yields a relatively high value or benefit per unit when used against or applied to another entity.
-
E.
hasProportion
chosen
Indicates that one entity stands in a specified ratio, fraction, or relative share to another entity or whole.
- 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.