Triple
T32196025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | folinic acid |
E822405
|
entity |
| Predicate | activeIsomer |
P181082
|
FINISHED |
| Object | L-folinic acid |
—
|
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: L-folinic acid | Statement: [folinic acid, activeIsomer, L-folinic acid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeIsomer Context triple: [folinic acid, activeIsomer, L-folinic acid]
-
A.
isomer
Indicates that two chemical species share the same molecular formula but differ in the arrangement or orientation of their atoms, resulting in distinct structures or properties.
-
B.
isEnantiomerOf
Indicates that two molecular entities are non-superimposable mirror images of each other, related by inversion of all chiral centers.
-
C.
isChiral
Indicates that an entity and its mirror image are not superimposable, reflecting a handedness or asymmetry in its structure.
-
D.
hasStereoselectivity
Indicates that a reaction or process preferentially forms or involves one stereoisomer over others.
-
E.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: May 1, 2026, 12:35 a.m.