Triple

T33150527
Position Surface form Disambiguated ID Type / Status
Subject Franklin Pierce Lake E848421 entity
Predicate createdBy P806 FINISHED
Object Franklin Pierce Dam
Franklin Pierce Dam is a flood-control and water-storage structure in New Hampshire that impounds the Contoocook River to form Franklin Pierce Lake.
E2286693 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: Franklin Pierce Dam | Statement: [Franklin Pierce Lake, createdBy, Franklin Pierce Dam]
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: Franklin Pierce Dam
Triple: [Franklin Pierce Lake, createdBy, Franklin Pierce Dam]
Generated description
Franklin Pierce Dam is a flood-control and water-storage structure in New Hampshire that impounds the Contoocook River to form Franklin Pierce Lake.

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_69f3495a458c8190a1d34b237ba0be3f completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d894b1d48190b2523614bc5df916 completed May 3, 2026, 5:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a46d45b36b88190babff0854b70f7eb completed July 2, 2026, 9:12 p.m.
NEDg Description generation batch_6a46d7d70f70819099044f0bd856950c completed July 2, 2026, 9:27 p.m.
NED2 Entity disambiguation (via description) batch_6a46d8ac9f04819096312e590e319dff completed July 2, 2026, 9:31 p.m.
Created at: May 1, 2026, 1:28 a.m.