Triple
T23931499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenwich, Massachusetts |
E602509
|
entity |
| Predicate | cemeteriesRelocatedTo |
P60564
|
FINISHED |
| Object | Quabbin Park Cemetery |
—
|
NE NERFINISHED |
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: Quabbin Park Cemetery | Statement: [Greenwich, Massachusetts, cemeteriesRelocatedTo, Quabbin Park Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteriesRelocatedTo Context triple: [Greenwich, Massachusetts, cemeteriesRelocatedTo, Quabbin Park Cemetery]
-
A.
laterBurialsMovedTo
Indicates that burials that occurred at a later time were relocated from their original site to another place.
-
B.
originalBurialSiteOfRemainsLaterMovedTo
chosen
Indicates that a location was the initial burial site of human remains that were subsequently relocated to another place.
-
C.
associatedCemetery
Indicates that there is a relationship linking an entity (such as a person, event, or organization) to a specific cemetery with which it is connected.
-
D.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
E.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf9c223881908e5fa4b5564848e6 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:58 p.m.