Triple
T27807072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JNM Hospital |
E702407
|
entity |
| Predicate | majorHospitalFor |
P37248
|
FINISHED |
| Object | Kalyani |
—
|
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: Kalyani | Statement: [JNM Hospital, majorHospitalFor, Kalyani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorHospitalFor Context triple: [JNM Hospital, majorHospitalFor, Kalyani]
-
A.
majorHospital
chosen
Indicates that a hospital holds a primary or leading status within a healthcare system or region, typically due to its size, capacity, or range of services.
-
B.
designatedAsFlagshipHospitalFor
Indicates that one hospital has been officially selected or recognized as the primary or leading flagship institution for another entity (such as a health system, region, or organization).
-
C.
servesAsPrimaryTeachingHospitalFor
Indicates that one institution functions as the main clinical training and teaching site for another institution, typically a medical school or academic program.
-
D.
hospitalLocation
Indicates the geographic place or address where a hospital is situated.
-
E.
containsHospital
Indicates that one entity includes or encompasses a hospital within its boundaries or composition.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 27, 2026, 5:39 p.m.