Triple

T27800458
Position Surface form Disambiguated ID Type / Status
Subject Kokořín Valley E702225 entity
Predicate hasWatercourse P165 FINISHED
Object Pšovka River
The Pšovka River is a small river in the Central Bohemian Region of the Czech Republic, known for flowing through the scenic sandstone landscape of the Kokořín Valley.
E1842200 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: Pšovka River | Statement: [Kokořín Valley, hasWatercourse, Pšovka 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: Pšovka River
Triple: [Kokořín Valley, hasWatercourse, Pšovka River]
Generated description
The Pšovka River is a small river in the Central Bohemian Region of the Czech Republic, known for flowing through the scenic sandstone landscape of the Kokořín Valley.

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_69ef8408e0588190977cffa32dc33a29 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6383625cc8190aa223d8ef655743c completed May 2, 2026, 5:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24ec17307c81908b0bccd381477e1d completed June 7, 2026, 3:57 a.m.
NEDg Description generation batch_6a24f1b9b9008190b3bad9eadfdfb4f8 completed June 7, 2026, 4:21 a.m.
NED2 Entity disambiguation (via description) batch_6a24f58fc4b481908784675c0203e96b completed June 7, 2026, 4:37 a.m.
Created at: April 27, 2026, 5:34 p.m.