Triple
T26352062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casey Hospital |
E662927
|
entity |
| Predicate | publicHealthcareFacility |
P19124
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Casey Hospital, publicHealthcareFacility, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicHealthcareFacility Context triple: [Casey Hospital, publicHealthcareFacility, true]
-
A.
clinicalFacilities
Indicates that one entity provides, contains, or is associated with clinical facilities used for medical or healthcare services by another entity.
-
B.
hospitalLocation
Indicates the geographic place or address where a hospital is situated.
-
C.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
D.
hospitalFunction
Indicates the specific medical or administrative role, service, or operational purpose that a hospital performs.
-
E.
isPublicHospital
chosen
Indicates that a hospital is owned, funded, or operated by a government or public authority rather than by private entities.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 26, 2026, 10:46 p.m.