Triple

T15123139
Position Surface form Disambiguated ID Type / Status
Subject Ely, Minnesota E361216 entity
Predicate hasNearbyLake P17985 FINISHED
Object Burntside Lake
Burntside Lake is a large, clear, island-dotted recreational lake in northern Minnesota known for fishing, boating, and its proximity to the Boundary Waters Canoe Area Wilderness.
E1896975 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: Burntside Lake | Statement: [Ely, Minnesota, hasNearbyLake, Burntside 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: Burntside Lake
Triple: [Ely, Minnesota, hasNearbyLake, Burntside Lake]
Generated description
Burntside Lake is a large, clear, island-dotted recreational lake in northern Minnesota known for fishing, boating, and its proximity to the Boundary Waters Canoe Area Wilderness.

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_69d85a06450081909c5a14ea9851a15e completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e005a0c6888190840de4ead2306544 completed April 15, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2731fef5c881909209ad80d7c8cbda completed June 8, 2026, 9:19 p.m.
NEDg Description generation batch_6a2734a2a5288190a36884ba35e1f0ac completed June 8, 2026, 9:31 p.m.
NED2 Entity disambiguation (via description) batch_6a273511f38c81908e827ec7b699cd12 completed June 8, 2026, 9:33 p.m.
Created at: April 10, 2026, 3:06 a.m.