Triple

T8092637
Position Surface form Disambiguated ID Type / Status
Subject Kinross-shire E188904 entity
Predicate contains P35 FINISHED
Object Kinnesswood E396438 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: Kinnesswood | Statement: [Kinross-shire, contains, Kinnesswood]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kinnesswood
Context triple: [Kinross-shire, contains, Kinnesswood]
  • A. Kinnesswood chosen
    Kinnesswood is a small village in Perth and Kinross, Scotland, situated near Loch Leven and known for its scenic rural setting.
  • B. Kingussie
    Kingussie is a small town in the Scottish Highlands that serves as a local hub and rail stop on the route between Edinburgh and Inverness.
  • C. Raploch
    Raploch is a residential district and regeneration area in the city of Stirling in central Scotland.
  • D. Ecclefechan
    Ecclefechan is a small village in Dumfries and Galloway in southwest Scotland, noted as the birthplace of the writer and historian Thomas Carlyle.
  • E. Aberlemno
    Aberlemno is a small Scottish village best known for its remarkable collection of early medieval Pictish standing stones.
  • 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_69ca82b7b3e88190b9041ab0ef28b3cb completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb42217a1881909792b08a2f06fb75 completed March 31, 2026, 3:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd3438ae2481909549a05f195cda39 completed April 1, 2026, 3:05 p.m.
Created at: March 30, 2026, 5:30 p.m.