Triple

T22817891
Position Surface form Disambiguated ID Type / Status
Subject Roxburgh Dam E565148 entity
Predicate locatedNear P294 FINISHED
Object Roxburgh 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: Roxburgh | Statement: [Roxburgh Dam, locatedNear, Roxburgh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Roxburgh
Context triple: [Roxburgh Dam, locatedNear, Roxburgh]
  • A. Roxburgh
    Roxburgh is a historic area in the Scottish Borders that was once a significant medieval royal burgh and fortress.
  • B. Roxburgh chosen
    Roxburgh is a small town in Central Otago, New Zealand, known for its fruit orchards, hydroelectric dam, and scenic setting in the Clutha River valley.
  • C. Elphinstone
    Elphinstone is a small village in East Lothian, Scotland, known for its rural character and proximity to the town of Tranent.
  • D. Sholto
    Sholto is a masculine given name of Scottish origin, historically associated with figures such as military leaders and nobles.
  • E. Kincorth
    Kincorth is a residential area in the south of Aberdeen, Scotland, known for its post-war housing and proximity to the River Dee.
  • 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_69e2458426188190b58b8ab4844fe420 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17dcd7da481909d591f145382725b completed April 29, 2026, 3:41 a.m.
Created at: April 17, 2026, 3:33 p.m.