Triple
T20602940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulmicort |
E506227
|
entity |
| Predicate | fullEffectTime |
P48090
|
FINISHED |
| Object | may take 1 to 2 weeks of regular use |
—
|
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: may take 1 to 2 weeks of regular use | Statement: [Pulmicort, fullEffectTime, may take 1 to 2 weeks of regular use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullEffectTime Context triple: [Pulmicort, fullEffectTime, may take 1 to 2 weeks of regular use]
-
A.
effectDuration
Indicates the length of time for which an effect remains active or valid.
-
B.
temporaryEffect
Indicates that one entity causes or experiences an effect that is limited in duration and does not produce a lasting change.
-
C.
temporalEffect
chosen
Indicates a relationship where one event, state, or action produces consequences or changes that occur at a later time.
-
D.
eraDuration
Indicates the length of time that a particular era or period spans.
-
E.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa22663881909a8d4644e1c48dc2 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.