Triple

T14084670
Position Surface form Disambiguated ID Type / Status
Subject Yalding E338959 entity
Predicate locatedOnRiver P165 FINISHED
Object River Teise E272573 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 Teise | Statement: [Yalding, locatedOnRiver, River Teise]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Teise
Context triple: [Yalding, locatedOnRiver, River Teise]
  • A. River Teise chosen
    River Teise is a small river in Kent, England, known for flowing through the Weald and joining the River Medway near Yalding.
  • B. 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.
  • C. River Tâf
    The River Tâf is a river in southwest Wales that flows through Carmarthenshire before emptying into Carmarthen Bay.
  • D. Esaro River
    The Esaro River is a watercourse in the Calabria region of southern Italy, known for flowing through the province of Crotone before reaching the Ionian Sea.
  • E. River Tanat
    River Tanat is a river in Powys, Wales, known for flowing through the Tanat Valley before joining the River Vyrnwy.
  • 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_69d81c687b0c819087fd9ed4198403f8 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5ede40048190b465e909565730c1 completed April 14, 2026, 3:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd0a3e55c81909b52f618e9076dd2 completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:21 p.m.