Triple
T37099008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maimonides Medical Center |
E918643
|
entity |
| Predicate | hasCardiacSurgeryProgram |
P58392
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Maimonides Medical Center, hasCardiacSurgeryProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCardiacSurgeryProgram Context triple: [Maimonides Medical Center, hasCardiacSurgeryProgram, yes]
-
A.
hasCardiacCareUnit
Indicates that an entity (such as a hospital or medical facility) includes or is equipped with a specialized cardiac care unit for treating heart-related conditions.
-
B.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
C.
hasHealthProgram
chosen
Indicates that an entity provides, administers, or is associated with a specific health-related program or initiative.
-
D.
hasPatientInFirstHeartTransplant
Indicates that the subject is the patient involved in the first heart transplant procedure performed by the object.
-
E.
hasPrimaryAblationProcess
Indicates that an entity is associated with or undergoes a specific main method or process of ablation as its primary means of removal or destruction.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:14 p.m.