Triple

T1660033
Position Surface form Disambiguated ID Type / Status
Subject OS Explorer 392 E35883 entity
Predicate coversArea P175 FINISHED
Object Lochaber region E35881 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: Lochaber region | Statement: [OS Explorer 392, coversArea, Lochaber region]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lochaber region
Context triple: [OS Explorer 392, coversArea, Lochaber region]
  • A. Forfarshire
    Forfarshire is the former historic name of the Scottish county now known as Angus.
  • B. Highlands region
    The Highlands region is a mountainous inland area of Papua New Guinea known for its rugged terrain, cool climate, and diverse traditional cultures.
  • C. Lochaber chosen
    Lochaber is a region in the western Scottish Highlands known for its rugged landscapes, including Britain’s highest mountain, Ben Nevis.
  • D. Highland
    Highland is a suburban city in Southern California’s Inland Empire, located in San Bernardino County near the city of San Bernardino.
  • E. Dumfriesshire
    Dumfriesshire is a historic county in the Southern Uplands of Scotland, known for its rural landscapes, market towns, and borderland history.
  • 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_69a88606aa808190aa0b421b4271f220 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa6277b11481909a894391f4feadd0 completed March 6, 2026, 5:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69adb5b7247c81909224f04af68c3a5d completed March 8, 2026, 5:45 p.m.
Created at: March 4, 2026, 7:29 p.m.