Triple
T3002933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Rea |
E81830
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Moseley Brook |
E322150
|
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: Moseley Brook | Statement: [River Rea, hasTributary, Moseley Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moseley Brook Context triple: [River Rea, hasTributary, Moseley Brook]
-
A.
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.
-
B.
Bourn Brook
chosen
Bourn Brook is a small watercourse in Birmingham, England, that flows through urban and suburban areas before joining the River Rea.
-
C.
Hebble Brook
Hebble Brook is a small river in West Yorkshire, England, that flows through the town of Halifax and joins the River Calder.
-
D.
Letcombe Brook
Letcombe Brook is a small chalk stream in Oxfordshire, England, valued for its clear waters, rich wildlife, and role in the local landscape around Wantage.
-
E.
Pymmes Brook
Pymmes Brook is a small urban stream in North London that flows through several boroughs before joining the River Lea.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a1371c481909e214234afed1a65 |
completed | March 8, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1f8629c7c8190b597255ab8f391af |
completed | March 11, 2026, 11:18 p.m. |
Created at: March 8, 2026, 2:59 p.m.