Triple
T9815005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embankment Road |
E238379
|
entity |
| Predicate | follows |
P134
|
FINISHED |
| Object | River Plym |
E65563
|
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 Plym | Statement: [Embankment Road, follows, River Plym]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Plym Context triple: [Embankment Road, follows, River Plym]
-
A.
River Plym
chosen
River Plym is a river in Devon, England, that flows through Dartmoor and into Plymouth Sound, giving its name to the city of Plymouth.
-
B.
River Devon
River Devon is a small river in central Scotland that flows through Clackmannanshire before joining the River Forth.
-
C.
River Devon
The River Devon is a river in central England that flows through Leicestershire and Nottinghamshire before joining the River Trent.
-
D.
River Whye
River Whye is a fictional river in Stephen King’s Dark Tower universe, flowing through the central realm known as Mid-World.
-
E.
River Torridge
River Torridge is a river in north Devon, England, known for flowing through towns like Great Torrington and Bideford before reaching the Bristol 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f19660819083e3f15780352052 |
completed | April 2, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc67db68819093217c9a74e72fbf |
completed | April 5, 2026, 2:43 a.m. |
Created at: March 30, 2026, 8:30 p.m.