Triple
T29392622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Elizabeths Hospital East Campus Cemetery |
E745407
|
entity |
| Predicate | burialPopulationIncludes |
P135783
|
FINISHED |
| Object | psychiatric patients |
—
|
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 patients | Statement: [St. Elizabeths Hospital East Campus Cemetery, burialPopulationIncludes, psychiatric patients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialPopulationIncludes Context triple: [St. Elizabeths Hospital East Campus Cemetery, burialPopulationIncludes, psychiatric patients]
-
A.
hasBurialPopulation
chosen
Indicates that a burial site or context contains or is associated with a specified number or group of interred individuals.
-
B.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
C.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
E.
containsHeartBurial
Indicates that one entity includes or features the burial of a heart within it.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669fff6488190ae591e1c99dfeed8 |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:43 p.m.