Triple
T21469691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poynton Brook |
E529691
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Poynton 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: Poynton Brook | Statement: [Poynton Brook, hasName, Poynton Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poynton Brook Context triple: [Poynton Brook, hasName, Poynton Brook]
-
A.
Poynton Brook
chosen
Poynton Brook is a small watercourse in Cheshire, England, that flows through the village of Poynton and forms part of its local river network.
-
B.
Heathcote Brook
Heathcote Brook is a small stream in central New Jersey that feeds into the Millstone River as part of the Raritan River watershed.
-
C.
Langden Brook
Langden Brook is a small watercourse in Lancashire, England, that flows through the Forest of Bowland before joining the River Hodder.
-
D.
Bourn Brook
Bourn Brook is a small watercourse in Birmingham, England, that flows through urban and suburban areas before joining the River Rea.
-
E.
Henmore Brook
Henmore Brook is a small watercourse in Derbyshire, England, that flows through the town of Ashbourne before joining the River Dove.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea12d9048190bf51ca3efc435a64 |
completed | April 23, 2026, 9:44 a.m. |
Created at: April 16, 2026, 6:16 p.m.