Triple
T2138629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xolair |
E46709
|
entity |
| Predicate | hasMolecularTarget |
P37016
|
FINISHED |
| Object | circulating IgE |
—
|
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: circulating IgE | Statement: [Xolair, hasMolecularTarget, circulating IgE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMolecularTarget Context triple: [Xolair, hasMolecularTarget, circulating IgE]
-
A.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
B.
isProdrugOf
Indicates that one substance is a precursor form that is metabolized in the body to produce the active form of another substance.
-
C.
hasMolecularWeight
Indicates that an entity possesses a specific molecular weight value, typically expressed in standardized units such as daltons or g/mol.
-
D.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
-
E.
hasPharmacologicClass
Indicates that a drug or medicinal product belongs to a specific pharmacologic class based on its mechanism of action or therapeutic effect.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf71edf08190add69022aabfd49d |
completed | March 7, 2026, 6:02 a.m. |
Created at: March 4, 2026, 7:44 p.m.