Triple
T11032876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverside Cemetery (Jewish) |
E260800
|
entity |
| Predicate | allowsBurialOf |
P25159
|
FINISHED |
| Object | Jewish individuals |
—
|
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: Jewish individuals | Statement: [Riverside Cemetery (Jewish), allowsBurialOf, Jewish individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsBurialOf Context triple: [Riverside Cemetery (Jewish), allowsBurialOf, Jewish individuals]
-
A.
possiblyBurialOf
Indicates that one entity is a potential or uncertain burial site, grave, or interment location associated with another entity.
-
B.
deniedBurialBy
Indicates that one entity refused or withheld permission for another entity to be buried.
-
C.
usedForBurialOf
chosen
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
D.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
E.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e650b48190967c53f54e3464ad |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.