Triple

T27274352
Position Surface form Disambiguated ID Type / Status
Subject Konda River E688143 entity
Predicate hasTributary P415 FINISHED
Object Yevra River
The Yevra River is a lesser-known watercourse in Russia that serves as a tributary within the Konda River basin in Western Siberia.
 E2283536 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: Yevra River | Statement: [Konda River, hasTributary, Yevra 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: Yevra River
Triple: [Konda River, hasTributary, Yevra River]
Generated description
The Yevra River is a lesser-known watercourse in Russia that serves as a tributary within the Konda River basin in Western Siberia.

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_69ef3558cf8881909595ef89daf6e14a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f6272737c08190b3d33f2c92fdf2ff completed May 2, 2026, 4:32 p.m.
NED1 Entity disambiguation (via context triple) batch_6a425eb5f0d88190b51e939633690159 completed June 29, 2026, 12:01 p.m.
NEDg Description generation batch_6a425fc6d9e88190b317ef2f38e63fb5 completed June 29, 2026, 12:06 p.m.
NED2 Entity disambiguation (via description) batch_6a426027e0e48190a46129307bd022a7 completed June 29, 2026, 12:08 p.m.
Created at: April 27, 2026, 11:01 a.m.