Triple
T3469573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Halton |
E73220
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Preston Brook |
E198524
|
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: Preston Brook | Statement: [Borough of Halton, containsSettlement, Preston Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Preston Brook Context triple: [Borough of Halton, containsSettlement, Preston Brook]
-
A.
Preston Brook
chosen
Preston Brook is a village in Cheshire, England, historically significant as a key junction and terminus on the British canal network.
-
B.
Bentley Brook
Bentley Brook is a small watercourse in Derbyshire, England, that feeds into the River Derwent as one of its tributary streams.
-
C.
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.
-
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.
Shuttleworth Brook
Shuttleworth Brook is a small watercourse in Lancashire, England, that serves as a minor tributary within the River Calder catchment.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb392f6481908b6ad0457b8cf421 |
completed | March 8, 2026, 6:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3680a23e0819088851295a605a085 |
completed | March 13, 2026, 1:27 a.m. |
Created at: March 8, 2026, 3:17 p.m.