Triple
T10292189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | thalidomide |
E241389
|
entity |
| Predicate | originalIndication |
P23162
|
FINISHED |
| Object | sedative |
—
|
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: sedative | Statement: [thalidomide, originalIndication, sedative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalIndication Context triple: [thalidomide, originalIndication, sedative]
-
A.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
B.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
C.
indicatedFor
chosen
Indicates...that one entity (typically a treatment, procedure, or product) is recommended or appropriate for use in relation to another entity (such as a condition, symptom, or patient group).
-
D.
originalFeature
Indicates that one entity is the initial or source feature from which another feature is derived, modified, or referenced.
-
E.
originallyPresentedAs
Indicates that one entity was first introduced, described, or characterized in the form or manner specified by 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.