Triple
T5117887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter Street Cemetery |
E115381
|
entity |
| Predicate | usedForBurialsUntil |
P50093
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Charter Street Cemetery, usedForBurialsUntil, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForBurialsUntil Context triple: [Charter Street Cemetery, usedForBurialsUntil, 19th century]
-
A.
usedForBurialOf
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
B.
usedAsGraveUntil
chosen
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.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
E.
buriedFor
Indicates that one entity is buried on behalf of, in honor of, or as a memorial for another entity.
- 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_69bd4442ade0819087b9461f892b206b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:41 p.m.