Triple
T1172180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vumerity |
E24937
|
entity |
| Predicate | commonAdverseEffect |
P23164
|
FINISHED |
| Object | flushing |
—
|
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: flushing | Statement: [Vumerity, commonAdverseEffect, flushing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonAdverseEffect Context triple: [Vumerity, commonAdverseEffect, flushing]
-
A.
hasCommonAdverseEffect
chosen
Indicates that two or more entities share at least one adverse effect that occurs in response to them.
-
B.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
C.
involvedPhysicalEffect
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
-
D.
hasContraindication
Indicates that one entity (such as a treatment, drug, or procedure) should not be used or performed in the presence of another entity (such as a condition, factor, or co-medication) because it may cause harm or adverse effects.
-
E.
disadvantage
Indicates that one entity is in a less favorable, weaker, or hindered position relative to another in a given context.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bceb3f188190b8b767380fe5986f |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.