Triple
T8357229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillain–Barré syndrome |
E196711
|
entity |
| Predicate | hasOnsetPattern |
P77983
|
FINISHED |
| Object | rapidly progressive |
—
|
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: rapidly progressive | Statement: [Guillain–Barré syndrome, hasOnsetPattern, rapidly progressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnsetPattern Context triple: [Guillain–Barré syndrome, hasOnsetPattern, rapidly progressive]
-
A.
hasOnsetTypes
Indicates the types or categories of onset (e.g., how or when something begins) that are associated with a given entity or condition.
-
B.
hasOnset
Indicates the point in time or condition at which a process, event, or state begins.
-
C.
onsetRate
chosen
Indicates the rate at which an event, condition, or process begins or develops over time.
-
D.
hasLateOnsetForm
Indicates that an entity has a variant or form that manifests or becomes apparent later in life or at a relatively advanced stage.
-
E.
hasEarlyOnsetForm
Indicates that the related condition, trait, or phenomenon occurs in an early-onset form, typically manifesting earlier in life than usual.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804b57f88190907a4e4e389caf5f |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.