Triple

T29294217
Position Surface form Disambiguated ID Type / Status
Subject Ústí nad Orlicí District E742775 entity
Predicate contains P35 FINISHED
Object Tichá Orlice River
The Tichá Orlice River is a river in the Czech Republic that flows through the Pardubice Region and is one of the headwaters of the Orlice River.
E2294216 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: Tichá Orlice River | Statement: [Ústí nad Orlicí District, contains, Tichá Orlice 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: Tichá Orlice River
Triple: [Ústí nad Orlicí District, contains, Tichá Orlice River]
Generated description
The Tichá Orlice River is a river in the Czech Republic that flows through the Pardubice Region and is one of the headwaters of the Orlice River.

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_69f0912323c48190b9a24ef8cf359225 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f66542901c8190a34ece2e73b93744 completed May 2, 2026, 8:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7bb91c69808190ad2eb2b9f9f79345 completed Aug. 12, 2026, 12:06 a.m.
NEDg Description generation batch_6a7bba2886708190b217cce5fc751ca5 completed Aug. 12, 2026, 12:11 a.m.
NED2 Entity disambiguation (via description) batch_6a7bbac46b688190a91acdeb000bc81a completed Aug. 12, 2026, 12:13 a.m.
Created at: April 28, 2026, 1:04 p.m.