Triple
T17396882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliot Burying Ground, Roxbury |
E422976
|
entity |
| Predicate | hasGravestonesFromPeriod |
P87860
|
FINISHED |
| Object | colonial era |
—
|
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: colonial era | Statement: [Eliot Burying Ground, Roxbury, hasGravestonesFromPeriod, colonial era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGravestonesFromPeriod Context triple: [Eliot Burying Ground, Roxbury, hasGravestonesFromPeriod, colonial era]
-
A.
hasGraveMarkersFromPeriod
chosen
Indicates that an entity possesses grave markers that date from, or are associated with, a specified historical period.
-
B.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
C.
hasNotablePeriodOfUseAsCemetery
Indicates that something was significantly used as a cemetery during a particular period of time.
-
D.
hasGravestone
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
E.
timePeriodOfBurials
Indicates the span of time during which the burials associated with an entity took place.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abd9b748190bd55c863276d9e3a |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.