Triple

T21402681
Position Surface form Disambiguated ID Type / Status
Subject Stevenston E527950 entity
Predicate historicalRegion P915 FINISHED
Object Cunninghame 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: Cunninghame | Statement: [Stevenston, historicalRegion, Cunninghame]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cunninghame
Context triple: [Stevenston, 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. Banavie
    Banavie is a small Scottish village near Fort William, known for its proximity to Neptune’s Staircase on the Caledonian Canal and views of Ben Nevis.
  • D. Machanshyre
    Machanshyre is a historical Scottish territorial division associated with the lordship encompassing the areas of Machanshyre and Polmont.
  • E. Lethington
    Lethington is the historic name of Lennoxlove House, a notable Scottish country house with medieval origins and strong ties to prominent Scottish families.
  • 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_69e0b520ee3c8190abddbee7e37e834c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b171336c819083ae5e2c0f5d4b95 completed April 22, 2026, 11:30 a.m.
Created at: April 16, 2026, 5:24 p.m.