Triple
T8722341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bachelor’s Grove Cemetery |
E207041
|
entity |
| Predicate | usedAsBurialGroundUntil |
P84274
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Bachelor’s Grove Cemetery, usedAsBurialGroundUntil, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBurialGroundUntil Context triple: [Bachelor’s Grove Cemetery, usedAsBurialGroundUntil, mid-20th century]
-
A.
usedAsCemeterySince
Indicates that a place has functioned as a cemetery starting from a specified point in time.
-
B.
usedAsGraveUntil
Indicates that something continued to function or be designated as a grave up to a specified point in time.
-
C.
burialsUntil
Indicates the number of burial events that remain or are scheduled to occur up to a specified point in time or condition.
-
D.
periodOfBurial
Indicates the time period or date range during which the burial of an entity took place.
-
E.
eraOfMostBurials
Indicates the historical time period during which the greatest number of burials occurred for a given site or context.
- F. None of above. chosen
Provenance (4 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d0609f48190adc56226724b16c6 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:36 p.m.