Triple

T11637589
Position Surface form Disambiguated ID Type / Status
Subject Scottish Borders E276565 entity
Predicate containsHistoricRegion P915 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: [Scottish Borders, containsHistoricRegion, Peeblesshire]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Peeblesshire
Context triple: [Scottish Borders, containsHistoricRegion, 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. Machanshyre
    Machanshyre is a historical Scottish territorial division associated with the lordship encompassing the areas of Machanshyre and Polmont.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a25d80208190b33e95db2e7cc276 completed April 10, 2026, 7:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69ee87d006e881908e008ffa17502d47 completed April 26, 2026, 9:46 p.m.
Created at: April 8, 2026, 9:39 p.m.