Triple

T21310086
Position Surface form Disambiguated ID Type / Status
Subject Assunpink Creek E525305 entity
Predicate hasWaterbodyOnCourse P56309 FINISHED
Object Stone Tavern Lake
Stone Tavern Lake is a man-made reservoir in central New Jersey known for fishing, boating, and wildlife within the Assunpink Wildlife Management Area.
E2292074 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: Stone Tavern Lake | Statement: [Assunpink Creek, hasWaterbodyOnCourse, Stone Tavern Lake]
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: Stone Tavern Lake
Triple: [Assunpink Creek, hasWaterbodyOnCourse, Stone Tavern Lake]
Generated description
Stone Tavern Lake is a man-made reservoir in central New Jersey known for fishing, boating, and wildlife within the Assunpink Wildlife Management Area.

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_69e0b518b8948190ad69cf9a8784d397 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75aaa56fc81909ba7649302528269 completed April 21, 2026, 11:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5cbb9fba208190a8c89adc08ff3fbd completed July 19, 2026, 11:57 a.m.
NEDg Description generation batch_6a5cbc19ad70819091b041d57ea1df1d completed July 19, 2026, 11:59 a.m.
NED2 Entity disambiguation (via description) batch_6a5cbc728d748190a5470818c88c132b completed July 19, 2026, noon
Created at: April 16, 2026, 4:06 p.m.