Triple
T243542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United First Parish Church, Quincy, Massachusetts |
E4985
|
entity |
| Predicate | burialChamberLocation |
P196
|
FINISHED |
| Object | crypt beneath the 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 beneath the church | Statement: [United First Parish Church, Quincy, Massachusetts, burialChamberLocation, crypt beneath the church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialChamberLocation Context triple: [United First Parish Church, Quincy, Massachusetts, burialChamberLocation, crypt beneath the church]
-
A.
burialCoordinates
Indicates the geographic location where an entity is buried, typically expressed as spatial coordinates.
-
B.
burialPlace
chosen
Indicates the location where a person or entity is buried.
-
C.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
D.
resurrectionPlace
Indicates the location where an entity is brought back to life or restored from death.
-
E.
mainChamber
Indicates that something is the primary or central chamber or room within a larger structure or system.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b62839c8190824064fe5da6a92a |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.