Triple
T31490160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berghof sanatorium |
E803384
|
entity |
| Predicate | patientCharacter |
P59096
|
FINISHED |
| Object | Hans Castorp |
—
|
NE NERFINISHED |
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: Hans Castorp | Statement: [Berghof sanatorium, patientCharacter, Hans Castorp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patientCharacter Context triple: [Berghof sanatorium, patientCharacter, Hans Castorp]
-
A.
patientPortrayedBy
Indicates that a patient is represented or depicted by a particular actor, model, or illustrative figure.
-
B.
patientContribution
Indicates that a patient provides, supplies, or participates with some resource, information, or effort toward a medical or healthcare-related activity or outcome.
-
C.
formerPatient
Indicates that one entity was previously a patient of another entity but is no longer under their care.
-
D.
primaryPatientType
chosen
Indicates the main category or classification of patient that is primarily associated with or targeted by an entity, action, or service.
-
E.
hasPatient
Indicates that an action, event, or process involves a specific entity as the one undergoing or receiving its effects (the patient).
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e4ca4881908146cb7b170209d6 |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:37 p.m.