Triple
T6345409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grove Street Cemetery |
E142730
|
entity |
| Predicate | hasNumberOfBurials |
P14555
|
FINISHED |
| Object | over 14,000 |
—
|
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: over 14,000 | Statement: [Grove Street Cemetery, hasNumberOfBurials, over 14,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfBurials Context triple: [Grove Street Cemetery, hasNumberOfBurials, over 14,000]
-
A.
numberOfBurials
chosen
Indicates the total count of burial events associated with a given entity.
-
B.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
C.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
E.
hasBurialSections
Indicates that one entity (typically a burial ground or cemetery) is divided into or associated with specific burial sections.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067b7e0d08190abacaf41c08ed15e |
completed | March 22, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.