Triple
T2137030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford |
E46676
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | Great Stour |
E46677
|
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: Great Stour | Statement: [Ashford, hasRiver, Great Stour]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Great Stour Context triple: [Ashford, hasRiver, Great Stour]
-
A.
River Darent
River Darent is a chalk stream river in Kent, England, flowing north through the Darent Valley to join the River Thames.
-
B.
Werse
The Werse is a river in North Rhine-Westphalia, Germany, known for flowing through the Münster region before joining the Ems.
-
C.
River Wey
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.
-
D.
River Rother
The River Rother is a river in central England that flows through Derbyshire and South Yorkshire before joining the River Don.
-
E.
River Stour
chosen
The River Stour is a major river in southeast England that flows through the county of Kent, passing historic towns such as Canterbury before reaching the English Channel.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbdff9254819094d27405478e29a0 |
completed | March 7, 2026, 5:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afb66209bc8190aa030b147e4d34cb |
completed | March 10, 2026, 6:12 a.m. |
Created at: March 4, 2026, 7:44 p.m.