Triple
T900244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A25 road |
E19429
|
entity |
| Predicate | crosses |
P416
|
FINISHED |
| Object | River Wey |
E26186
|
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 Wey | Statement: [A25 road, crosses, River Wey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Wey Context triple: [A25 road, crosses, River Wey]
-
A.
River Wey
chosen
The River Wey is a tributary of the River Thames in southern England, flowing through Hampshire and Surrey and historically important for navigation and trade.
-
B.
River Great Ouse
The River Great Ouse is one of the major rivers in eastern England, flowing through several counties and historic towns before reaching The Wash on the North Sea.
-
C.
River Darent
River Darent is a chalk stream river in Kent, England, flowing north through the Darent Valley to join the River Thames.
-
D.
River Kennet
River Kennet is a significant chalk stream in southern England that flows through Wiltshire and Berkshire before joining the River Thames.
-
E.
River Foulness
The River Foulness is a river in eastern England that drains parts of Lincolnshire and Nottinghamshire before joining the River Trent.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad42ecac81909f8bc554d2fe0363 |
completed | March 1, 2026, 9:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac93a1fc5c819089ab10a6f0ed062b |
completed | March 7, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.