Triple
T8372332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntington's chorea |
E197487
|
entity |
| Predicate | typicalLifeExpectancyAfterOnset |
P22711
|
FINISHED |
| Object | about 15 to 20 years |
—
|
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: about 15 to 20 years | Statement: [Huntington's chorea, typicalLifeExpectancyAfterOnset, about 15 to 20 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLifeExpectancyAfterOnset Context triple: [Huntington's chorea, typicalLifeExpectancyAfterOnset, about 15 to 20 years]
-
A.
typicalAgingTime
Indicates the usual duration required for something to age or mature under normal conditions.
-
B.
averageSurvivalAfterDiagnosis
chosen
Indicates the typical length of time individuals survive following the point at which a condition or disease is first diagnosed.
-
C.
lifeExpectancyLevel
Indicates the typical or average length of life expected for an entity, often expressed as a comparative or categorical level.
-
D.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
-
E.
typicalMaximumAge
Indicates the usual upper age limit that an entity is expected or allowed to reach under normal conditions.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a6944081909c4547688c9e70ae |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.