Triple
T26205018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | norepinephrine |
E655337
|
entity |
| Predicate | isSynthesizedFrom |
P151192
|
FINISHED |
| Object | L-tyrosine |
—
|
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-tyrosine | Statement: [norepinephrine, isSynthesizedFrom, L-tyrosine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSynthesizedFrom Context triple: [norepinephrine, isSynthesizedFrom, L-tyrosine]
-
A.
wasFirstSynthesizedBy
Indicates that one entity is the person, group, or organization that originally synthesized or created the other entity for the first time.
-
B.
synthesizedAs
Indicates that one entity is produced or created in the form of another entity through a synthesis process.
-
C.
wasFirstSynthesizedIn
Indicates the location or context in which something (typically a substance or compound) was originally created or produced for the first time.
-
D.
synthesizedWhen
Indicates that one entity is produced or formed as a result of a process or condition occurring at a particular time or under specific circumstances.
-
E.
isProducedFrom
chosen
Indicates that something is created, generated, or derived from a specified source or input.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cde512c819094036b09613ff330 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:50 p.m.