Triple
T16852050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvoni |
E409697
|
entity |
| Predicate | hasRouteOfElimination |
P54020
|
FINISHED |
| Object | biliary excretion |
—
|
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: biliary excretion | Statement: [Harvoni, hasRouteOfElimination, biliary excretion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteOfElimination Context triple: [Harvoni, hasRouteOfElimination, biliary excretion]
-
A.
hasEliminationRoute
chosen
Indicates that there exists a specific pathway or method by which something can be removed, discharged, or otherwise eliminated from a system or context.
-
B.
isStrategicRouteFor
Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
-
C.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
D.
hadRoute
Indicates that an entity (such as a service, vehicle, or system) followed, operated on, or was associated with a specific route.
-
E.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37abadc81909d02d329403497d6 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.