Triple
T1169544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALS |
E24881
|
entity |
| Predicate | hasMedianSurvival |
P22711
|
FINISHED |
| Object | 2–5 years after symptom onset |
—
|
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: 2–5 years after symptom onset | Statement: [ALS, hasMedianSurvival, 2–5 years after symptom onset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedianSurvival Context triple: [ALS, hasMedianSurvival, 2–5 years after symptom onset]
-
A.
averageSurvivalAfterDiagnosis
chosen
Indicates the typical length of time individuals survive following the point at which a condition or disease is first diagnosed.
-
B.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
C.
hasSurvivorTerm
Indicates that an entity is associated with a term or label specifically used to describe survivors of an event, condition, or circumstance.
-
D.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
E.
hasSurvivors
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bce821b481908bc278a3fa7973f4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.