Triple
T290357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent |
E5977
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Thames Estuary |
E36675
|
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: Thames Estuary | Statement: [Kent, borders, Thames Estuary]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thames Estuary Context triple: [Kent, borders, Thames Estuary]
-
A.
Thames Estuary
chosen
The Thames Estuary is the broad tidal mouth of the River Thames where it meets the North Sea, forming a major shipping route and ecological zone in southeast England.
-
B.
Severn
The Severn is the longest river in Great Britain, flowing through Wales and England before emptying into the Bristol Channel.
-
C.
Thames
The Thames is a major river in southern England that flows through London and has long been central to the country’s history, commerce, and culture.
-
D.
Bristol Channel
The Bristol Channel is a major inlet of the Atlantic Ocean separating South Wales from southwest England and providing access to the Severn Estuary.
-
E.
River Mersey
The River Mersey is a major river in North West England that flows through cities including Manchester and Liverpool before emptying into the Irish Sea.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e4f78bc81909a64fd6aaec3b504 |
completed | Feb. 28, 2026, 3:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3e56fd6b88190b18e081386436ea9 |
completed | March 1, 2026, 7:06 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.