Triple
T5055698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adur District |
E113896
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | River Adur |
E195813
|
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 Adur | Statement: [Adur District, river, River Adur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Adur Context triple: [Adur District, river, River Adur]
-
A.
River Adur
chosen
The River Adur is a river in West Sussex, England, that flows through the South Downs to reach the English Channel at Shoreham-by-Sea.
-
B.
River Rother
The River Rother is a river in central England that flows through Derbyshire and South Yorkshire before joining the River Don.
-
C.
River Rother
River Rother is a river in East Sussex, England, that flows through the Weald to the English Channel near the town of Rye.
-
D.
River Brent
The River Brent is a tributary of the River Thames in West London, flowing through several London boroughs and giving its name to the London Borough of Brent.
-
E.
River Darent
River Darent is a chalk stream river in Kent, England, flowing north through the Darent Valley to join the River Thames.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd744e45588190beaa2f96bb2f41e2 |
completed | March 20, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf186790248190bc94cfbecf3cfe73 |
completed | March 21, 2026, 10:15 p.m. |
Created at: March 20, 2026, 1:38 p.m.