Triple
T23650575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasigna |
E584154
|
entity |
| Predicate | requiresFastingAdministration |
P74374
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tasigna, requiresFastingAdministration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresFastingAdministration Context triple: [Tasigna, requiresFastingAdministration, true]
-
A.
hasFastingRule
chosen
Indicates that there is a prescribed rule or requirement regarding fasting that applies to the subject.
-
B.
hasObligationOfFasting
Indicates that one entity is required or duty-bound to perform fasting.
-
C.
fastingDuration
Indicates the length of time that an entity abstains from eating (and possibly drinking), typically as part of a fasting practice.
-
D.
fastingIncludes
Indicates that a period of fasting encompasses or contains a specified component, practice, or time interval as part of that fast.
-
E.
requiresPremedication
Indicates that one entity must receive premedication (a preparatory medical treatment) before another specified procedure, treatment, or action can occur.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b357d1108190802bc29e0ed7f097 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.