Triple
T7126917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Roch |
E166085
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object |
Ashworth Brook
Ashworth Brook is a small watercourse in Greater Manchester, England, that serves as a tributary of the River Roch within the region’s local river network.
|
E647999
|
NE FINISHED |
How this triple was built (4 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: Ashworth Brook | Statement: [River Roch, hasTributary, Ashworth Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashworth Brook Context triple: [River Roch, hasTributary, Ashworth Brook]
-
A.
Shuttleworth Brook
Shuttleworth Brook is a small watercourse in Lancashire, England, that serves as a minor tributary within the River Calder catchment.
-
B.
Hebble Brook
Hebble Brook is a small river in West Yorkshire, England, that flows through the town of Halifax and joins the River Calder.
-
C.
Bourn Brook
Bourn Brook is a small watercourse in Birmingham, England, that flows through urban and suburban areas before joining the River Rea.
-
D.
Henmore Brook
Henmore Brook is a small watercourse in Derbyshire, England, that flows through the town of Ashbourne before joining the River Dove.
-
E.
Quorn Brook
Quorn Brook is a small watercourse in Leicestershire, England, that serves as a tributary of the River Soar.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Ashworth Brook Triple: [River Roch, hasTributary, Ashworth Brook]
Generated description
Ashworth Brook is a small watercourse in Greater Manchester, England, that serves as a tributary of the River Roch within the region’s local river network.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Ashworth Brook Target entity description: Ashworth Brook is a small watercourse in Greater Manchester, England, that serves as a tributary of the River Roch within the region’s local river network.
-
A.
Shuttleworth Brook
Shuttleworth Brook is a small watercourse in Lancashire, England, that serves as a minor tributary within the River Calder catchment.
-
B.
Hebble Brook
Hebble Brook is a small river in West Yorkshire, England, that flows through the town of Halifax and joins the River Calder.
-
C.
Bourn Brook
Bourn Brook is a small watercourse in Birmingham, England, that flows through urban and suburban areas before joining the River Rea.
-
D.
Henmore Brook
Henmore Brook is a small watercourse in Derbyshire, England, that flows through the town of Ashbourne before joining the River Dove.
-
E.
Quorn Brook
Quorn Brook is a small watercourse in Leicestershire, England, that serves as a tributary of the River Soar.
- F. None of above. chosen
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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e64ee8ac81909ee1c7cb1db3af33 |
completed | March 27, 2026, 8:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7bf7c0bb88190ac03e2279512d837 |
completed | March 28, 2026, 11:46 a.m. |
| NEDg | Description generation | batch_69c7bfe7143481908c4da6b67f47f19e |
completed | March 28, 2026, 11:47 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c7c05fd088819083df4c7167216ca2 |
completed | March 28, 2026, 11:49 a.m. |
Created at: March 27, 2026, 2:44 p.m.