Triple
T2662060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. John’s Church (Richmond, Virginia) |
E54745
|
entity |
| Predicate | burialsInclude |
P25054
|
FINISHED |
| Object | prominent Richmond citizens |
—
|
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: prominent Richmond citizens | Statement: [St. John’s Church (Richmond, Virginia), burialsInclude, prominent Richmond citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialsInclude Context triple: [St. John’s Church (Richmond, Virginia), burialsInclude, prominent Richmond citizens]
-
A.
burials
chosen
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
D.
containsHeartBurial
Indicates that one entity includes or features the burial of a heart within it.
-
E.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd969eff08190a206ad6424ba34d6 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.