Triple
T5425229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | relapsing-remitting multiple sclerosis |
E121346
|
entity |
| Predicate | relapseDuration |
P51072
|
FINISHED |
| Object | at least 24 hours |
—
|
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: at least 24 hours | Statement: [relapsing-remitting multiple sclerosis, relapseDuration, at least 24 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relapseDuration Context triple: [relapsing-remitting multiple sclerosis, relapseDuration, at least 24 hours]
-
A.
durationOfAffliction
chosen
Indicates the length of time that an affliction or condition persists for an entity.
-
B.
alternativeDuration
Indicates that there is an additional or substitute time span associated with an event or activity, differing from its primary or standard duration.
-
C.
periodOfRevival
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
D.
reentryDate
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
E.
readmissionYear
Indicates the calendar year in which a subject is readmitted after a prior discharge or departure.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.