Triple

T27365960
Position Surface form Disambiguated ID Type / Status
Subject Eresma River E690162 entity
Predicate hasTributary P415 FINISHED
Object Voltoya River
The Voltoya River is a watercourse in central Spain that flows through the provinces of Ávila and Segovia before joining the Eresma River within the Duero basin.
 E2293058 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: Voltoya River | Statement: [Eresma River, hasTributary, Voltoya 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: Voltoya River
Triple: [Eresma River, hasTributary, Voltoya River]
Generated description
The Voltoya River is a watercourse in central Spain that flows through the provinces of Ávila and Segovia before joining the Eresma River within the Duero 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_69ef51ff826081909e42c8e2bfb97941 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62c5ccd048190b6fa467a3034aa51 completed May 2, 2026, 4:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7a5eba673c81909493811b421dccdd completed Aug. 10, 2026, 11:28 p.m.
NEDg Description generation batch_6a7a6255cf8c81909a96a740f5c98a4c completed Aug. 10, 2026, 11:44 p.m.
NED2 Entity disambiguation (via description) batch_6a7a62ef24c48190a9d301cc52f56578 completed Aug. 10, 2026, 11:46 p.m.
Created at: April 27, 2026, 12:17 p.m.