Triple
T26205033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | norepinephrine |
E655337
|
entity |
| Predicate | isClearedBy |
P160041
|
FINISHED |
| Object | NET |
—
|
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: NET | Statement: [norepinephrine, isClearedBy, NET]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClearedBy Context triple: [norepinephrine, isClearedBy, NET]
-
A.
isClearedBy
Indicates that one entity removes an obstruction, restriction, or pending status from another entity, allowing it to proceed or be considered resolved.
-
B.
isClearedThrough
Indicates that something has been officially approved, authorized, or allowed to proceed by passing through a required review or clearance process.
-
C.
clearedOf
Indicates that an entity has been officially found not responsible for, or freed from suspicion of, a previously alleged wrongdoing, charge, or negative condition.
-
D.
clearingSystem
Indicates that one entity functions as the financial clearing mechanism or infrastructure used to settle transactions for another entity.
-
E.
siteClearedBy
Indicates that a particular site has been cleared or prepared as a result of actions performed by a specified agent or entity.
- 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_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. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 8:50 p.m.