Triple
T24979374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosehill Cemetery Company |
E625119
|
entity |
| Predicate | managesHistoricSite |
P127891
|
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, managesHistoricSite, Rosehill Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesHistoricSite Context triple: [Rosehill Cemetery Company, managesHistoricSite, Rosehill Cemetery]
-
A.
servesHistoricSites
Indicates that an entity provides services, access, or support specifically to historic sites.
-
B.
stateHistoricSiteManagedBy
Indicates that a designated state historic site is administered, overseen, or operated by a particular managing organization or authority.
-
C.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
D.
heritageSiteCustodianOf
chosen
Indicates that an entity serves as the official manager, guardian, or responsible authority for the care, protection, and oversight of a heritage site.
-
E.
heritageSiteOwned
Indicates that one entity owns, controls, or holds legal title to a heritage site.
- 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_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:02 a.m.