Triple
T22620977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Wick |
E558276
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | River Wick |
—
|
NE NERFINISHED |
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 Wick | Statement: [River Wick, hasName, River Wick]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Wick Context triple: [River Wick, hasName, River Wick]
-
A.
River Wick
chosen
River Wick is a small river in northern Scotland that flows through the town of Wick before entering the North Sea.
-
B.
River Gaywood
River Gaywood is a small river in Norfolk, England, that flows through the town of King’s Lynn before joining the Great Ouse.
-
C.
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.
-
D.
River Dean
River Dean is a small river in Cheshire, England, that flows through the town of Bollington and the surrounding countryside.
-
E.
River Werre
River Werre is a river in North Rhine-Westphalia, Germany, that flows through the Teutoburg Forest region and several towns before joining the Weser.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e39959481909e0ae67379435f95 |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 3 p.m.