Triple
T16535059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Street |
E401669
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | River Ver |
E212053
|
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 Ver | Statement: [Park Street, near, River Ver]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Ver Context triple: [Park Street, near, River Ver]
-
A.
River Ver
chosen
The River Ver is a small chalk stream in Hertfordshire, England, flowing through St Albans before joining the River Colne.
-
B.
River Wid
The River Wid is a small river in Essex, England, that flows through rural landscapes before joining the River Crouch.
-
C.
River Sem
River Sem is a small river in Wiltshire, England, that flows through the Sem Valley before joining the River Nadder.
-
D.
IVER
IVER is a village and civil parish in Buckinghamshire, England, known for its proximity to London and the Pinewood Studios film complex.
-
E.
River Nar
The River Nar is a small river in Norfolk, England, that flows through the countryside to join the River Great Ouse near King’s Lynn.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e345574d88819094548367bf983078 |
completed | April 18, 2026, 8:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006093244081909ae74674de966d6d |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:15 a.m.