Triple
T23317975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totley Brook |
E590762
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Totley Brook |
—
|
NE NERFINISHED |
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: Totley Brook | Statement: [Totley Brook, hasName, Totley Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Totley Brook Context triple: [Totley Brook, hasName, Totley Brook]
-
A.
Totley Brook
chosen
Totley Brook is a small watercourse in South Yorkshire, England, that flows through the Totley area before joining the River Sheaf.
-
B.
Turnford Brook
Turnford Brook is a local watercourse in the Turnford area of Hertfordshire, England, forming part of the region’s network of small rivers and streams.
-
C.
Finnington Brook
Finnington Brook is a small watercourse in Lancashire, England, that serves as a tributary within the local River Roddlesworth catchment.
-
D.
Langden Brook
Langden Brook is a small watercourse in Lancashire, England, that flows through the Forest of Bowland before joining the River Hodder.
-
E.
Wealdstone Brook
Wealdstone Brook is a small urban stream in northwest London that serves as a tributary of the River Brent, flowing through areas such as Harrow and Wealdstone.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197828c408190ae071624e40de4cc |
completed | April 29, 2026, 5:30 a.m. |
Created at: April 17, 2026, 5:07 p.m.