Triple
T26205029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | norepinephrine |
E655337
|
entity |
| Predicate | isReleasedFrom |
P5043
|
FINISHED |
| Object | adrenal medulla |
—
|
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: adrenal medulla | Statement: [norepinephrine, isReleasedFrom, adrenal medulla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReleasedFrom Context triple: [norepinephrine, isReleasedFrom, adrenal medulla]
-
A.
leasedFrom
Indicates that one entity is renting or leasing something from another entity, which acts as the owner or lessor.
-
B.
releaseFrom
Indicates that one entity causes or authorizes another entity to be freed, discharged, or removed from a prior state of confinement, obligation, or restriction.
-
C.
releaseOf
chosen
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
D.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
-
E.
releaseObtainedBy
Indicates that a particular release results from, or is produced through, a specified obtaining or acquisition process.
- 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_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 8:50 p.m.