Triple

T20043822
Position Surface form Disambiguated ID Type / Status
Subject Blà Bheinn E497498 entity
Predicate isInCouncilArea P962 FINISHED
Object Highland 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: Highland | Statement: [Blà Bheinn, isInCouncilArea, Highland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Highland
Context triple: [Blà Bheinn, isInCouncilArea, Highland]
  • A. Highland chosen
    Highland is a vast council area in the Scottish Highlands known for its rugged landscapes, remote communities, and iconic natural scenery including mountains, lochs, and coastline.
  • B. Highland
    Highland is a suburban city in Southern California’s Inland Empire, located in San Bernardino County near the city of San Bernardino.
  • C. Highland
    Highland is a commuter rail station on the Needham Line serving passengers in the Boston, Massachusetts area.
  • D. Highland
    Highland is a city in Utah County, Utah, known as a suburban residential community in the Provo–Orem metropolitan area.
  • E. Highlands
    The Highlands is a rugged, sparsely populated region of northern Scotland known for its dramatic mountains, glens, and lochs, as well as its strong Gaelic cultural heritage.
  • 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_69da627278c88190babe4297a9df1236 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e662ed59bc8190a9ff25493e500ebb completed April 20, 2026, 5:31 p.m.
Created at: April 11, 2026, 3:37 p.m.