Triple
T34091422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fenfluramine |
E874310
|
entity |
| Predicate | hasFormerIndication |
P29363
|
FINISHED |
| Object | obesity |
—
|
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: obesity | Statement: [fenfluramine, hasFormerIndication, obesity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerIndication Context triple: [fenfluramine, hasFormerIndication, obesity]
-
A.
hasIndication
Indicates that one entity (typically a product, treatment, or intervention) is intended, approved, or suitable for use in addressing, preventing, or managing a particular condition, purpose, or circumstance.
-
B.
previousIndication
Indicates that one indication or sign occurred earlier in time than another, serving as a prior instance or precursor in a sequence of indications.
-
C.
hasFormerUse
chosen
Indicates that something previously served a particular function or role that it no longer has.
-
D.
hasPriorHistory
Indicates that an entity has a previously recorded occurrence, condition, or involvement relevant to the current context.
-
E.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:52 a.m.