Triple

T35559041
Position Surface form Disambiguated ID Type / Status
Subject River Boyne drainage basin E1027585 entity
Predicate containsTributary P415 FINISHED
Object Stoneyford River
The Stoneyford River is a minor watercourse in Ireland that serves as one of the tributaries feeding into the larger River Boyne system.
E2297826 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: Stoneyford River | Statement: [River Boyne drainage basin, containsTributary, Stoneyford 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: Stoneyford River
Triple: [River Boyne drainage basin, containsTributary, Stoneyford River]
Generated description
The Stoneyford River is a minor watercourse in Ireland that serves as one of the tributaries feeding into the larger River Boyne system.

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_69f76e014fd481909e9f04ac603a2aa9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79841d13881909bc5b1eeb3346ed5 completed May 3, 2026, 6:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a83dbf1c8a48190a4c99637a056e296 completed Aug. 18, 2026, 4:13 a.m.
NEDg Description generation batch_6a83dc4fffdc8190a4c1d70abad85992 completed Aug. 18, 2026, 4:15 a.m.
NED2 Entity disambiguation (via description) batch_6a83dc62e66081909ada72ee5312f4c4 completed Aug. 18, 2026, 4:15 a.m.
Created at: May 3, 2026, 4:04 p.m.