Triple

T15986449
Position Surface form Disambiguated ID Type / Status
Subject Columbia Lions men's rowing E387706 entity
Predicate homeBodyOfWater P1778 FINISHED
Object Overpeck Lake
Overpeck Lake is a man-made reservoir and recreational waterway in Bergen County, New Jersey, known for rowing, kayaking, and other outdoor activities.
E2042613 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: Overpeck Lake | Statement: [Columbia Lions men's rowing, homeBodyOfWater, Overpeck 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: Overpeck Lake
Triple: [Columbia Lions men's rowing, homeBodyOfWater, Overpeck Lake]
Generated description
Overpeck Lake is a man-made reservoir and recreational waterway in Bergen County, New Jersey, known for rowing, kayaking, and other outdoor activities.

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_69d86daa562c81908aacc179c0fe8fb5 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e157589d78819091f7b9b1081dd6ad completed April 16, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a352f92c63c819098035a4d045b0a0a completed June 19, 2026, 12:01 p.m.
NEDg Description generation batch_6a3533aaf1d881909e9f0981fae87c6d completed June 19, 2026, 12:18 p.m.
NED2 Entity disambiguation (via description) batch_6a35341981848190941fffd6dd22b4c1 completed June 19, 2026, 12:20 p.m.
Created at: April 10, 2026, 4:54 a.m.