Triple

T37440198
Position Surface form Disambiguated ID Type / Status
Subject Pawtuckaway Lake E930393 entity
Predicate hasAlternativeName P39 FINISHED
Object Pawtuckaway Pond
Pawtuckaway Pond is a popular recreational lake in Nottingham, New Hampshire, known for its islands, coves, and surrounding Pawtuckaway State Park.
E2236449 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: Pawtuckaway Pond | Statement: [Pawtuckaway Lake, hasAlternativeName, Pawtuckaway Pond]
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: Pawtuckaway Pond
Triple: [Pawtuckaway Lake, hasAlternativeName, Pawtuckaway Pond]
Generated description
Pawtuckaway Pond is a popular recreational lake in Nottingham, New Hampshire, known for its islands, coves, and surrounding Pawtuckaway State Park.

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_69f76ebfdcb8819098562ff3db673b04 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb8dd9c0688190b07bd66f8b831db5 completed May 6, 2026, 6:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40afce40c88190bcbd6aeee55472b3 completed June 28, 2026, 5:23 a.m.
NEDg Description generation batch_6a40b29b69a08190972ab8e43c8ee972 completed June 28, 2026, 5:35 a.m.
NED2 Entity disambiguation (via description) batch_6a40b2fbc3b08190ab328d55f86ca094 completed June 28, 2026, 5:36 a.m.
Created at: May 3, 2026, 4:17 p.m.