Triple

T20093189
Position Surface form Disambiguated ID Type / Status
Subject Sand River Convention E496327 entity
Predicate signedAt P441 FINISHED
Object Sand River 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: Sand River | Statement: [Sand River Convention, signedAt, Sand River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sand River
Context triple: [Sand River Convention, signedAt, Sand River]
  • A. Sand River chosen
    Sand River is a historical location in South Africa known as the site where the 1852 Sand River Convention was signed, recognizing the independence of the Transvaal Boer republic.
  • B. Sand River
    Sand River is a scenic waterway in Ontario, Canada, known for its waterfalls, rugged shoreline, and hiking trails within Lake Superior Provincial Park.
  • C. Sandela River
    The Sandela River is a watercourse in northern Poland that flows through the town of Lubawa.
  • D. Saane River
    The Saane River is a Swiss river that flows through the canton of Fribourg and joins the Aare, contributing significantly to the region’s landscape and hydrology.
  • E. Vechte River
    The Vechte River is a waterway in northwestern Germany and the eastern Netherlands that flows through Lower Saxony and Overijssel before joining the Zwarte Water near Zwolle.
  • 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66668db8881908c43b1deef9af1d3 completed April 20, 2026, 5:46 p.m.
Created at: April 11, 2026, 11:22 p.m.