Triple
T21946161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pat Peoples |
E541938
|
entity |
| Predicate | undergoesTreatmentAt |
P8558
|
FINISHED |
| Object | psychiatric facility |
—
|
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: psychiatric facility | Statement: [Pat Peoples, undergoesTreatmentAt, psychiatric facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergoesTreatmentAt Context triple: [Pat Peoples, undergoesTreatmentAt, psychiatric facility]
-
A.
treatmentLocation
chosen
Indicates the place or facility where a treatment or medical intervention is administered to an entity.
-
B.
hasReceivedTreatmentFor
Indicates that an entity has undergone or been given a treatment in relation to a specified condition, issue, or problem.
-
C.
placeOfReception
Indicates the location where something (such as a person, item, or message) is received or accepted.
-
D.
treatmentType
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
-
E.
usesTreatment
Indicates that one entity applies or employs a particular treatment or therapeutic method on or for another entity.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12427c2b48190949c41bd3be2d9f3 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:57 p.m.