Triple
T3031095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Test Valley district |
E82895
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object | River Test |
E93423
|
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 Test | Statement: [Test Valley district, hasRiver, River Test]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Test Context triple: [Test Valley district, hasRiver, River Test]
-
A.
River Test
chosen
The River Test is a renowned chalk stream in southern England celebrated for its clear waters and world-class fly fishing, particularly for trout.
-
B.
Ai River
Ai River is a river located in Japan’s Ibaraki Prefecture.
-
C.
River Sprint
The River Sprint is a fast-flowing river in Cumbria, England, known for running through the Lake District and contributing to the River Kent catchment.
-
D.
River Burn
River Burn is a small river in Norfolk, England, known for flowing through the village of Burnham Thorpe near the north Norfolk coast.
-
E.
River Can
River Can is a small river in Essex, England, that flows through the city of Chelmsford and forms part of the River Chelmer system.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aee2fec81908116939a8d773fc4 |
completed | March 8, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1eeec62208190912f35e209c7f9d9 |
completed | March 11, 2026, 10:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.