Triple

T21079309
Position Surface form Disambiguated ID Type / Status
Subject River Moyola E519317 entity
Predicate flowsThrough P225 FINISHED
Object Tobermore 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: Tobermore | Statement: [River Moyola, flowsThrough, Tobermore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tobermore
Context triple: [River Moyola, flowsThrough, Tobermore]
  • A. Tobermore chosen
    Tobermore is a small village in County Londonderry, Northern Ireland, known for its rural character and location within the Mid Ulster District.
  • B. Toft
    Toft is a rural estate and small settlement in Cheshire, England, known for its historic hall and proximity to the town of Knutsford.
  • C. Toft
    Toft is a small village in South Cambridgeshire, England, situated just west of Cambridge and known for its rural character and close-knit community.
  • D. Toft
    Toft is a location that serves as one end of the Yell Sound ferry connection in the Shetland Islands, Scotland.
  • E. Sandoway
    Sandoway is the former English name for Thandwe, a coastal town in Rakhine State, western Myanmar, known historically as an important seaport.
  • 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_69e0b506e59c8190849b71ed07929215 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e702d939e08190a37d7b7cc1872ad5 completed April 21, 2026, 4:53 a.m.
Created at: April 16, 2026, 2:49 p.m.