Triple
T5173079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Brent |
E116730
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Hendon |
E632143
|
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: Hendon | Statement: [River Brent, flowsThrough, Hendon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hendon Context triple: [River Brent, flowsThrough, Hendon]
-
A.
Hendon
Hendon is an English surname most notably associated with the fictional character Miles Hendon from Mark Twain’s novel "The Prince and the Pauper."
-
B.
Hendon
chosen
Hendon is a suburban district in the London Borough of Barnet, historically known for its aerodrome and role in early British aviation.
-
C.
Hendon
Hendon is a district of Sunderland in Tyne and Wear, England, known historically for its shipbuilding and industrial heritage.
-
D.
Harmondsworth
Harmondsworth is a village in the London Borough of Hillingdon, England, known for its historic Great Barn and proximity to Heathrow Airport.
-
E.
Balham
Balham is a residential district in south London, England, known for its vibrant high street, diverse community, and convenient transport links into central London.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd796f7c308190a721e33aabd499ac |
completed | March 20, 2026, 4:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7daed5d188190b499151e636d206d |
completed | March 28, 2026, 1:43 p.m. |
Created at: March 20, 2026, 1:45 p.m.