Triple
T14117235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepto-Bismol |
E339802
|
entity |
| Predicate | hasTypicalUseDuration |
P13716
|
FINISHED |
| Object | short-term treatment of acute symptoms |
—
|
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: short-term treatment of acute symptoms | Statement: [Pepto-Bismol, hasTypicalUseDuration, short-term treatment of acute symptoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalUseDuration Context triple: [Pepto-Bismol, hasTypicalUseDuration, short-term treatment of acute symptoms]
-
A.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
B.
durationOfUse
chosen
Indicates the length of time for which something is used or remains in use.
-
C.
typicalUseDays
Indicates the usual or expected number of days over which something is used or intended to be used.
-
D.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
E.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de609322ac8190bb389ca250882af5 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.