Triple

T22112136
Position Surface form Disambiguated ID Type / Status
Subject Milnthorpe E546442 entity
Predicate watercourse P415 FINISHED
Object River Bela 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 Bela | Statement: [Milnthorpe, watercourse, River Bela]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Bela
Context triple: [Milnthorpe, watercourse, River Bela]
  • A. River Bela chosen
    River Bela is a small river in Cumbria, England, flowing through the Arnside and Beetham area before entering the Kent estuary.
  • B. Berettyó River
    The Berettyó River is a tributary of the Körös River system in eastern Hungary and western Romania, flowing through agricultural plains and several towns before joining the Sebes-Körös.
  • C. Sebec River
    The Sebec River is a tributary in central Maine that drains Sebec Lake and flows westward to join the Piscataquis River within the larger Penobscot River system.
  • D. Rába River
    The Rába River is a Central European waterway flowing from Austria through western Hungary, historically significant as a strategic site in various military conflicts.
  • E. Berheci River
    The Berheci River is a watercourse in eastern Romania that serves as a tributary of the Bârlad River, flowing through rural areas and contributing to the region’s drainage basin.
  • 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1294ae7608190901745384a023bab completed April 28, 2026, 9:40 p.m.
Created at: April 16, 2026, 8:31 p.m.