Triple

T4673749
Position Surface form Disambiguated ID Type / Status
Subject Anglo-Scottish border E103626 entity
Predicate follows P134 FINISHED
Object River Sark E177204 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 Sark | Statement: [Anglo-Scottish border, follows, River Sark]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Sark
Context triple: [Anglo-Scottish border, follows, River Sark]
  • A. River Sark chosen
    The River Sark is a small river in the border region between England and Scotland that flows into the Solway Firth.
  • B. River Ock
    River Ock is a small river in Oxfordshire, England, that flows through the Vale of White Horse before joining the River Thames.
  • C. River Beult
    River Beult is a lowland river in Kent, England, known for its meandering course through rural farmland before joining the River Medway.
  • D. Gers River
    The Gers River is a waterway in southwestern France that flows through the Gers department, including the town of Auch, before joining the Garonne River.
  • E. River Havel
    The River Havel is a major waterway in northeastern Germany that flows through Berlin and Brandenburg, connecting several lakes and cities before joining the Elbe River.
  • 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_69bd43dda32c8190938b37744ca270fc completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd635326808190bd6909117aca1208 completed March 20, 2026, 3:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69be104e4aec8190a633b46eca1f434b completed March 21, 2026, 3:28 a.m.
Created at: March 20, 2026, 1:15 p.m.