Triple

T15265179
Position Surface form Disambiguated ID Type / Status
Subject Kincardineshire E364880 entity
Predicate borders P224 FINISHED
Object Forfarshire E18123 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: Forfarshire | Statement: [Kincardineshire, borders, Forfarshire]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Forfarshire
Context triple: [Kincardineshire, borders, Forfarshire]
  • A. Forfarshire chosen
    Forfarshire is the former historic name of the Scottish county now known as Angus.
  • B. Cromartyshire
    Cromartyshire was a historic county in the Scottish Highlands, known for its scattered enclaves and association with local clans such as Clan Urquhart.
  • C. Dumfriesshire
    Dumfriesshire is a historic county in the Southern Uplands of Scotland, known for its rural landscapes, market towns, and borderland history.
  • D. Elginshire
    Elginshire is a historic county in northeastern Scotland, centered on the town of Elgin and now largely corresponding to the modern council area of Moray.
  • E. Roxburghshire
    Roxburghshire is a historic county in the Scottish Borders, known for its rich medieval heritage and notable monastic sites.
  • 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_69d85a0f08408190b3c3259ae35d79d2 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00851c5b88190a296b6a105d3ee30 completed April 15, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff3649d1408190a4fed26539de1849 completed May 9, 2026, 1:27 p.m.
Created at: April 10, 2026, 3:14 a.m.