Triple
T23334228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Burn |
E591530
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | River Burn |
—
|
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 Burn | Statement: [River Burn, hasName, River Burn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Burn Context triple: [River Burn, hasName, River Burn]
-
A.
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.
-
B.
River Burn
River Burn is a small river in North Yorkshire, England, known for flowing through Wensleydale before joining the River Ure.
-
C.
River Rat
The River Rat is a small river in Suffolk, England, that flows through villages such as Rattlesden before joining the River Gipping.
-
D.
Đáy River
Đáy River is a significant river in northern Vietnam that flows through several provinces and districts, serving as an important waterway and agricultural resource.
-
E.
River Bogie
River Bogie is a small river in Aberdeenshire, Scotland, known for flowing through the town of Huntly and contributing to the region’s rural landscape and local heritage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197efd98c819083635a2b8440f3eb |
completed | April 29, 2026, 5:32 a.m. |
Created at: April 17, 2026, 5:16 p.m.