Triple

T27098798
Position Surface form Disambiguated ID Type / Status
Subject Bohumín E686383 entity
Predicate locatedInOrNextToBodyOfWater P1489 FINISHED
Object Lutyně River
The Lutyně River is a small river in the Moravian-Silesian Region of the Czech Republic that flows through the town of Bohumín before joining larger regional waterways.
E1807329 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: Lutyně River | Statement: [Bohumín, locatedInOrNextToBodyOfWater, Lutyně River]
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: Lutyně River
Triple: [Bohumín, locatedInOrNextToBodyOfWater, Lutyně River]
Generated description
The Lutyně River is a small river in the Moravian-Silesian Region of the Czech Republic that flows through the town of Bohumín before joining larger regional waterways.

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_69ef1489f8b481908e24a1985982bd26 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f623b493588190b447991baff1ce27 completed May 2, 2026, 4:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15e681c5e48190aa02a511f81f5f45 completed May 26, 2026, 6:29 p.m.
NEDg Description generation batch_6a15e9a6eee481908136f7071c1a0324 completed May 26, 2026, 6:42 p.m.
NED2 Entity disambiguation (via description) batch_6a15eb2c79448190a470645418751296 completed May 26, 2026, 6:49 p.m.
Created at: April 27, 2026, 8:46 a.m.