Triple
T31544685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | carbidopa |
E804842
|
entity |
| Predicate | primaryEliminationRoute |
P137275
|
FINISHED |
| Object | renal |
—
|
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: renal | Statement: [carbidopa, primaryEliminationRoute, renal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEliminationRoute Context triple: [carbidopa, primaryEliminationRoute, renal]
-
A.
primaryRouteOf
Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
-
B.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
C.
primaryRouteOfElimination
chosen
Indicates the main biological pathway or process through which a substance is removed or cleared from an organism.
-
D.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
E.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:07 p.m.