Triple
T10291979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | warfarin |
E241385
|
entity |
| Predicate | hasHigherINRTargetRange |
P13790
|
FINISHED |
| Object | 2.5–3.5 for some mechanical valves |
—
|
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: 2.5–3.5 for some mechanical valves | Statement: [warfarin, hasHigherINRTargetRange, 2.5–3.5 for some mechanical valves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHigherINRTargetRange Context triple: [warfarin, hasHigherINRTargetRange, 2.5–3.5 for some mechanical valves]
-
A.
isHighestRangeOf
Indicates that one entity represents the maximum or topmost range or interval within which another entity falls or is categorized.
-
B.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
C.
isHigherThan
chosen
Indicates that one entity has a greater value, level, or position than another entity.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
hasHigherNorm
Indicates that one entity’s norm (such as magnitude, length, or size under a given norm) is greater than that 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d35f048190a215493acdf1f718 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:42 a.m.