Triple
T10415479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Theatre fire |
E245502
|
entity |
| Predicate | burialSiteOfVictims |
P196
|
FINISHED |
| Object | crypt of Monumental Church |
—
|
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: crypt of Monumental Church | Statement: [Richmond Theatre fire, burialSiteOfVictims, crypt of Monumental Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialSiteOfVictims Context triple: [Richmond Theatre fire, burialSiteOfVictims, crypt of Monumental Church]
-
A.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
B.
burialPlace
chosen
Indicates the location where a person or entity is buried.
-
C.
memorializesVictimsFrom
Indicates that something serves as a memorial specifically honoring victims originating from a particular place or event.
-
D.
burialPlaceOfManyMembers
Indicates a location that serves as the burial site for multiple members of a particular group, family, or organization.
-
E.
notableMassKillingSite
Indicates that a place is recognized as a significant location where a mass killing or massacre occurred.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0f7d188190a60a7c3832c51515 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.