Triple

T18161765
Position Surface form Disambiguated ID Type / Status
Subject Verkhnedneprovsk E434781 entity
Predicate locatedNearConfluenceOf P11842 FINISHED
Object Samotkan River
The Samotkan River is a waterway in central Ukraine that flows near the city of Verkhnedneprovsk and forms part of the local Dnieper River basin.
E2106609 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: Samotkan River | Statement: [Verkhnedneprovsk, locatedNearConfluenceOf, Samotkan 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: Samotkan River
Triple: [Verkhnedneprovsk, locatedNearConfluenceOf, Samotkan River]
Generated description
The Samotkan River is a waterway in central Ukraine that flows near the city of Verkhnedneprovsk and forms part of the local Dnieper River basin.

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_69d8b90b7a188190b3fc7b8d4a6cd20a completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dec32530819099d906640a07e92c completed April 19, 2026, 1:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3748caf26c8190a94ac703f2914b52 completed June 21, 2026, 2:13 a.m.
NEDg Description generation batch_6a374a91d4f08190bc2df424a4136b3d completed June 21, 2026, 2:21 a.m.
NED2 Entity disambiguation (via description) batch_6a374b44cba88190999dede2bc2a408e completed June 21, 2026, 2:24 a.m.
Created at: April 10, 2026, 10:30 a.m.