Triple

T27110057
Position Surface form Disambiguated ID Type / Status
Subject Moyola River E686686 entity
Predicate hasTributary P415 FINISHED
Object Clady River
The Clady River is a watercourse in Northern Ireland that serves as a tributary within the Moyola River system, contributing to the region’s drainage and local landscape.
 E2291695 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: Clady River | Statement: [Moyola River, hasTributary, Clady 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: Clady River
Triple: [Moyola River, hasTributary, Clady River]
Generated description
The Clady River is a watercourse in Northern Ireland that serves as a tributary within the Moyola River system, contributing to the region’s drainage and local landscape.

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_69ef148accd48190b6ed6e13a15f2a4f completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f6240111c08190a863d9786d36af1d completed May 2, 2026, 4:19 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5c803d10d081908960ed2e255f335c completed July 19, 2026, 7:43 a.m.
NEDg Description generation batch_6a5c808b2b68819089d79151a2773169 completed July 19, 2026, 7:45 a.m.
NED2 Entity disambiguation (via description) batch_6a5c80a667dc819087c192baab8aeaa7 completed July 19, 2026, 7:45 a.m.
Created at: April 27, 2026, 8:53 a.m.