Triple

T30884850
Position Surface form Disambiguated ID Type / Status
Subject Ełk Lake E786729 entity
Predicate hasNameInLanguage P15 FINISHED
Object Jezioro Ełckie
Jezioro Ełckie is a picturesque lake in northeastern Poland, known for its recreational opportunities and its location by the town of Ełk in the Masurian Lake District.
E1944738 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: Jezioro Ełckie | Statement: [Ełk Lake, hasNameInLanguage, Jezioro Ełckie]
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: Jezioro Ełckie
Triple: [Ełk Lake, hasNameInLanguage, Jezioro Ełckie]
Generated description
Jezioro Ełckie is a picturesque lake in northeastern Poland, known for its recreational opportunities and its location by the town of Ełk in the Masurian Lake District.

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_69f224bbfa7c81908448e0c261c523e3 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69204be748190a6a2a401d81c1218 completed May 3, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a292af8ef4c8190928576822e52853f completed June 10, 2026, 9:14 a.m.
NEDg Description generation batch_6a292de433f08190a69526a2ea7447ca completed June 10, 2026, 9:27 a.m.
NED2 Entity disambiguation (via description) batch_6a292e525cb08190866c0d2af0c8fa3e completed June 10, 2026, 9:28 a.m.
Created at: April 29, 2026, 8:49 p.m.