Triple

T22516376
Position Surface form Disambiguated ID Type / Status
Subject voriconazole E556657 entity
Predicate hasRouteConsideration P148684 FINISHED
Object loading dose recommended for intravenous use 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: loading dose recommended for intravenous use | Statement: [voriconazole, hasRouteConsideration, loading dose recommended for intravenous use]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRouteConsideration
Context triple: [voriconazole, hasRouteConsideration, loading dose recommended for intravenous use]
  • A. hasRoute
    Indicates that there exists a path or connection enabling travel or communication from one entity to another.
  • B. hasNotableRoute
    Indicates that an entity (such as a transportation service or pathway) includes or is associated with a route that is considered significant, well-known, or otherwise noteworthy.
  • C. hasRouteInformation
    Indicates that there is associated data describing the path, directions, or connection details between locations or points.
  • D. isRouteOn
    Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
  • E. hasRouteStart
    Indicates that one entity serves as the starting point or origin location for a specified route associated with another 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_69e11e5657e881909f16ca58352c50da completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15e2cfc908190b3489228a1997f45 completed April 29, 2026, 1:26 a.m.
PD Predicate disambiguation batch_69ee625e3b408190a60c759fb0b28fe2 completed April 26, 2026, 7:07 p.m.
PDg Predicate description generation batch_69ee8841e9cc81908d23b34215e3be71 completed April 26, 2026, 9:48 p.m.
Created at: April 16, 2026, 8:50 p.m.