Triple
T4937055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dollar |
E110837
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | River Devon |
E151946
|
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 Devon | Statement: [Dollar, locatedOn, River Devon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Devon Context triple: [Dollar, locatedOn, River Devon]
-
A.
River Devon
The River Devon is a river in central England that flows through Leicestershire and Nottinghamshire before joining the River Trent.
-
B.
River Devon
chosen
River Devon is a small river in central Scotland that flows through Clackmannanshire before joining the River Forth.
-
C.
River Dart
The River Dart is a scenic river in Devon, England, known for flowing through Dartmoor to the English Channel and for its historic maritime and boating connections, including the naval town of Dartmouth.
-
D.
River Exe
The River Exe is a major river in Devon, England, flowing from Exmoor to the English Channel at Exmouth and shaping the landscapes and settlements along its estuary.
-
E.
River Plym
River Plym is a river in Devon, England, that flows through Dartmoor and into Plymouth Sound, giving its name to the city of Plymouth.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7085b1dc819099408f6503f0210f |
completed | March 20, 2026, 4:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bea46996c481908ec7b783ac9a20b1 |
completed | March 21, 2026, 2 p.m. |
Created at: March 20, 2026, 1:30 p.m.