Triple
T17026637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klara Sesemann |
E413080
|
entity |
| Predicate | laterHealthStatus |
P13710
|
FINISHED |
| Object | regains ability to walk |
—
|
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: regains ability to walk | Statement: [Klara Sesemann, laterHealthStatus, regains ability to walk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterHealthStatus Context triple: [Klara Sesemann, laterHealthStatus, regains ability to walk]
-
A.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of an entity.
-
C.
healthStatusBeforeDeath
Indicates the condition or state of an entity’s health immediately prior to its death.
-
D.
saluteStatus
Indicates the type or state of a salute being given or received between entities (e.g., whether, how, or in what manner one entity salutes another).
-
E.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d5ed388190871aa738cac04b65 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.