Triple
T11605879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Tanat |
E275257
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | River Tanat |
E275257
|
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 Tanat | Statement: [River Tanat, hasName, River Tanat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Tanat Context triple: [River Tanat, hasName, River Tanat]
-
A.
River Tanat
chosen
River Tanat is a river in Powys, Wales, known for flowing through the Tanat Valley before joining the River Vyrnwy.
-
B.
River Tâf
The River Tâf is a river in southwest Wales that flows through Carmarthenshire before emptying into Carmarthen Bay.
-
C.
Túr River
The Túr River is a watercourse in Eastern Europe that flows through parts of Romania and Hungary before joining the Tisa River.
-
D.
River Hodder
River Hodder is a river in Lancashire, England, known for flowing through the Forest of Bowland and joining the River Ribble near Great Mitton.
-
E.
River Brun
River Brun is a small river in Lancashire, England, that flows through the town of Burnley and contributes to its local landscape and waterways.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89551649c81908096ff392677442d |
completed | April 10, 2026, 6:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f08f811ff481908e2c14902a3361a2 |
completed | April 28, 2026, 10:44 a.m. |
Created at: April 8, 2026, 9:38 p.m.