Triple
T5391088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Most Holy Redeemer Cemetery, Baltimore, Maryland, United States |
E120329
|
entity |
| Predicate | hasBurialsOf |
P62966
|
FINISHED |
| Object | local parishioners |
—
|
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: local parishioners | Statement: [Most Holy Redeemer Cemetery, Baltimore, Maryland, United States, hasBurialsOf, local parishioners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialsOf Context triple: [Most Holy Redeemer Cemetery, Baltimore, Maryland, United States, hasBurialsOf, local parishioners]
-
A.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
B.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
C.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
-
D.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
E.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
- F. None of above. chosen
Provenance (4 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd87185f788190bd5244a1f7dbb5c8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd853005088190b1b092a9beb090b2 |
completed | March 20, 2026, 5:34 p.m. |
Created at: March 20, 2026, 2:04 p.m.