Triple
T16664674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brent Cross |
E404949
|
entity |
| Predicate | nearRiver |
P350
|
FINISHED |
| Object | River Brent |
E116730
|
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: River Brent | Statement: [Brent Cross, nearRiver, River Brent]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Brent Context triple: [Brent Cross, nearRiver, River Brent]
-
A.
River Brent
chosen
The River Brent is a tributary of the River Thames in West London, flowing through several London boroughs and giving its name to the London Borough of Brent.
-
B.
River Wick
River Wick is a small river in northern Scotland that flows through the town of Wick before entering the North Sea.
-
C.
River Lyde
The River Lyde is a small river in Hampshire, England, that flows through rural landscapes before joining the River Loddon.
-
D.
River Adur
The River Adur is a river in West Sussex, England, that flows through the South Downs to reach the English Channel at Shoreham-by-Sea.
-
E.
River Hodder
River Hodder is a river in Lancashire, England, known for flowing through the Forest of Bowland and joining the River Ribble near Great Mitton.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9be0688190afda306cde934c68 |
completed | April 18, 2026, 12:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0091901fd88190a3c0e4b133121a02 |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:18 a.m.