Triple
T24979383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosehill Cemetery Company |
E625119
|
entity |
| Predicate | operatesBurialGround |
P1496
|
FINISHED |
| Object | Rosehill Cemetery |
—
|
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: Rosehill Cemetery | Statement: [Rosehill Cemetery Company, operatesBurialGround, Rosehill Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesBurialGround Context triple: [Rosehill Cemetery Company, operatesBurialGround, Rosehill Cemetery]
-
A.
cemeteryOpened
Indicates that a cemetery began operating or was officially opened at a specific time.
-
B.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
C.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
D.
hasCemetery
chosen
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
E.
numberOfBurials
Indicates the total count of burial events associated with a given entity.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 18, 2026, 6:02 a.m.