Triple

T4991996
Position Surface form Disambiguated ID Type / Status
Subject Walkerburn E112152 entity
Predicate historicCounty P1069 FINISHED
Object Peeblesshire E167240 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: Peeblesshire | Statement: [Walkerburn, historicCounty, Peeblesshire]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Peeblesshire
Context triple: [Walkerburn, historicCounty, Peeblesshire]
  • A. Peeblesshire chosen
    Peeblesshire is a historic county in the Scottish Borders region of Scotland, known for its rural landscapes and the town of Peebles.
  • B. Kinross-shire
    Kinross-shire is a historic county in eastern Scotland, centered around the town of Kinross and the area near Loch Leven.
  • C. Cunninghame
    Cunninghame is a historic district in southwestern Scotland, traditionally forming part of Ayrshire.
  • D. Howdenshire
    Howdenshire is a historic rural district and former liberty in the East Riding of Yorkshire, England, centered around the town of Howden.
  • E. Stirlingshire
    Stirlingshire is a historic county in central Scotland centered on the city of Stirling, known for its strategic location and rich medieval and early modern history.
  • 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_69bd441be7bc8190b530362d427b97d2 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd729bb45081908d85891a9d9f4b71 completed March 20, 2026, 4:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be8a2d71c08190be1d3397585ca65c completed March 21, 2026, 12:08 p.m.
Created at: March 20, 2026, 1:34 p.m.