Triple
T4224222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Lee |
E94414
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Pymmes Brook |
E274320
|
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: Pymmes Brook | Statement: [River Lee, hasTributary, Pymmes Brook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pymmes Brook Context triple: [River Lee, hasTributary, Pymmes Brook]
-
A.
Pymmes Brook
chosen
Pymmes Brook is a small urban stream in North London that flows through several boroughs before joining the River Lea.
-
B.
Pipp Brook
Pipp Brook is a small river in Surrey, England, that flows through the town of Dorking before joining the River Mole.
-
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.
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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5b77294208190a53d6950dbf36351 |
completed | March 14, 2026, 7:30 p.m. |
Created at: March 12, 2026, 11:04 p.m.