Triple

T21176758
Position Surface form Disambiguated ID Type / Status
Subject McCook Lake, South Dakota E521832 entity
Predicate namedAfter P63 FINISHED
Object McCook Lake
McCook Lake is a small glacial lake and unincorporated community area in Union County, South Dakota, known for residential development and local recreation.
E2291629 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: McCook Lake | Statement: [McCook Lake, South Dakota, namedAfter, McCook 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: McCook Lake
Triple: [McCook Lake, South Dakota, namedAfter, McCook Lake]
Generated description
McCook Lake is a small glacial lake and unincorporated community area in Union County, South Dakota, known for residential development and local recreation.

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_69e0b50ef1d48190b063aa342667df22 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e730197cfc8190bde13453b761886b completed April 21, 2026, 8:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5c776f08948190b7e4bab900c6bb88 completed July 19, 2026, 7:06 a.m.
NEDg Description generation batch_6a5c77f7dd3c8190bb64b3f82b7d4464 completed July 19, 2026, 7:08 a.m.
NED2 Entity disambiguation (via description) batch_6a5c78738d2c819088ac60aa3d89a032 completed July 19, 2026, 7:10 a.m.
Created at: April 16, 2026, 3 p.m.