Triple

T8737264
Position Surface form Disambiguated ID Type / Status
Subject Enoch Poor E207416 entity
Predicate placeOfBirth P1 FINISHED
Object Dunstable, New Hampshire
Dunstable, New Hampshire was a former colonial-era town in southern New Hampshire that later contributed land to several present-day communities in the region.
E2282306 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: Dunstable, New Hampshire | Statement: [Enoch Poor, placeOfBirth, Dunstable, New Hampshire]
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: Dunstable, New Hampshire
Triple: [Enoch Poor, placeOfBirth, Dunstable, New Hampshire]
Generated description
Dunstable, New Hampshire was a former colonial-era town in southern New Hampshire that later contributed land to several present-day communities in the region.

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_69ca835a03a081909d4d4cd01a18c9fb completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5d45c96081909aa8509064ff3a04 completed March 31, 2026, 11:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a42158b39f88190ae5cf195f8738399 completed June 29, 2026, 6:49 a.m.
NEDg Description generation batch_6a4216c4f5ac8190aff47735e9eecf82 completed June 29, 2026, 6:55 a.m.
NED2 Entity disambiguation (via description) batch_6a4217206b508190ba1b578872c6b579 completed June 29, 2026, 6:56 a.m.
Created at: March 30, 2026, 6:38 p.m.