Triple

T24803038
Position Surface form Disambiguated ID Type / Status
Subject Old Village Cemetery (Dedham) E620579 entity
Predicate hasName P744 FINISHED
Object Old Village Cemetery
Old Village Cemetery is a historic burial ground in Dedham, Massachusetts, known for its early colonial-era graves and significance to the town’s heritage.
E1710306 NE 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: Old Village Cemetery | Statement: [Old Village Cemetery (Dedham), hasName, Old Village Cemetery]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Old Village Cemetery
Triple: [Old Village Cemetery (Dedham), hasName, Old Village Cemetery]
Generated description
Old Village Cemetery is a historic burial ground in Dedham, Massachusetts, known for its early colonial-era graves and significance to the town’s heritage.

Provenance (5 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_69e2fabf26bc8190b191faac8f67065b completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f412ab84288190b9c43aafc773c5bc completed May 1, 2026, 2:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1127185bb4819088a46534740ed77f completed May 23, 2026, 4:03 a.m.
NEDg Description generation batch_6a1134849eac8190a0f80898df1ae20c completed May 23, 2026, 5 a.m.
NED2 Entity disambiguation (via description) batch_6a11350decb88190b61a8491db612650 completed May 23, 2026, 5:03 a.m.
Created at: April 18, 2026, 4:49 a.m.