Triple

T6568693
Position Surface form Disambiguated ID Type / Status
Subject Southwest Scotland E155376 entity
Predicate historicalRegion P915 FINISHED
Object Cunninghame E440456 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: Cunninghame | Statement: [Southwest Scotland, historicalRegion, Cunninghame]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cunninghame
Context triple: [Southwest Scotland, historicalRegion, Cunninghame]
  • A. Cunninghame chosen
    Cunninghame is a historic district in southwestern Scotland, traditionally forming part of Ayrshire.
  • B. Linlithgowshire
    Linlithgowshire is the historic Scottish county that largely corresponds to the modern council area of West Lothian.
  • C. Machanshyre
    Machanshyre is a historical Scottish territorial division associated with the lordship encompassing the areas of Machanshyre and Polmont.
  • D. Lethington
    Lethington is the historic name of Lennoxlove House, a notable Scottish country house with medieval origins and strong ties to prominent Scottish families.
  • E. Dunnichen
    Dunnichen is a small rural village in eastern Scotland, historically noted as a possible site of the Battle of Dunnichen (Nechtansmere) in 685 AD.
  • 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_69c688151254819080387f87deab8fa7 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae54afd4819091ee65aca1de60a9 completed March 27, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6e4275eec8190ba52fa4fb1bc64db completed March 27, 2026, 8:10 p.m.
Created at: March 27, 2026, 1:53 p.m.