Triple
T8597769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Tavy |
E203593
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | River Burn |
E591530
|
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 Burn | Statement: [River Tavy, hasTributary, River Burn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Burn Context triple: [River Tavy, hasTributary, 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
chosen
River Burn is a small river in North Yorkshire, England, known for flowing through Wensleydale before joining the River Ure.
-
C.
Đá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.
-
D.
River Bain
The River Bain is a small river in North Yorkshire, England, known for flowing from Semerwater to join the River Ure near Bainbridge.
-
E.
River Bain
River Bain is a river in Lincolnshire, England, known for flowing through the town of Horncastle before joining the River Witham.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46cacbe88190b95beeedc9f480b0 |
completed | March 31, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebba872b8819098ba7525944bcce1 |
completed | April 2, 2026, 6:55 p.m. |
Created at: March 30, 2026, 6:24 p.m.