Triple

T37132345
Position Surface form Disambiguated ID Type / Status
Subject Jablonec nad Nisou District E919556 entity
Predicate contains P35 FINISHED
Object Souš Reservoir
Souš Reservoir is a man-made water reservoir in the Jizera Mountains of the Czech Republic, primarily used for drinking water supply and flood control.
E2286323 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: Souš Reservoir | Statement: [Jablonec nad Nisou District, contains, Souš Reservoir]
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: Souš Reservoir
Triple: [Jablonec nad Nisou District, contains, Souš Reservoir]
Generated description
Souš Reservoir is a man-made water reservoir in the Jizera Mountains of the Czech Republic, primarily used for drinking water supply and flood control.

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_69f76e9d13e48190a108f7fbf80ff375 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb303ee45081909794335fd8b2d27b completed May 6, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a469fc2472081909470e2d7805eaafc completed July 2, 2026, 5:28 p.m.
NEDg Description generation batch_6a46a1bb8d708190b4190000b10e75c4 completed July 2, 2026, 5:37 p.m.
NED2 Entity disambiguation (via description) batch_6a46a597aa24819084036fcc4bcb7955 completed July 2, 2026, 5:53 p.m.
Created at: May 3, 2026, 4:15 p.m.