Triple
T19157388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zetia |
E468959
|
entity |
| Predicate | mayReduce |
P9925
|
FINISHED |
| Object | triglyceride levels |
—
|
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: triglyceride levels | Statement: [Zetia, mayReduce, triglyceride levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayReduce Context triple: [Zetia, mayReduce, triglyceride levels]
-
A.
mayNotReduce
Indicates that one entity is prohibited from decreasing, diminishing, or lowering some quantity, quality, or resource associated with another entity.
-
B.
mayRemove
Indicates that one entity is permitted or authorized to remove another entity or its association.
-
C.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
D.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
E.
reduces
chosen
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeba91a081909c04d61d6117da06 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.