Triple
T34344242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central State Hospital Cemetery |
E881383
|
entity |
| Predicate | hasCommemorationActivity |
P82637
|
FINISHED |
| Object | memorial services |
—
|
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: memorial services | Statement: [Central State Hospital Cemetery, hasCommemorationActivity, memorial services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorationActivity Context triple: [Central State Hospital Cemetery, hasCommemorationActivity, memorial services]
-
A.
commemorativeActivities
chosen
Indicates activities carried out to honor, remember, or pay tribute to a person, event, or occasion.
-
B.
commemoratesActivity
Indicates that one entity serves to honor, remember, or mark the occurrence of a particular activity or event.
-
C.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
D.
hasCommemorationScope
Indicates the scope or extent of what is being commemorated in a commemoration-related relationship or event.
-
E.
commemorativeEvent
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.