Triple
T17831452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Wollaston Cemetery |
E445265
|
entity |
| Predicate | hasNotableBurialsRegion |
P3803
|
FINISHED |
| Object | New England figures |
—
|
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: New England figures | Statement: [Mount Wollaston Cemetery, hasNotableBurialsRegion, New England figures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBurialsRegion Context triple: [Mount Wollaston Cemetery, hasNotableBurialsRegion, New England figures]
-
A.
hasNotableBurials
chosen
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
B.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
C.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
D.
hasMassGraveOf
Indicates that a location or site contains a mass grave in which the referenced individuals or remains are buried.
-
E.
hasNotablePeriodOfUseAsCemetery
Indicates that something was significantly used as a cemetery during a particular period of time.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d248ecc8190b3f0d001b539d960 |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:15 a.m.