Triple

T22162901
Position Surface form Disambiguated ID Type / Status
Subject Sconser E547714 entity
Predicate hasCouncilArea P11102 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: [Sconser, hasCouncilArea, Highland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Highland
Context triple: [Sconser, hasCouncilArea, Highland]
  • A. Highland
    Highland is a suburban city in Southern California’s Inland Empire, located in San Bernardino County near the city of San Bernardino.
  • B. Highland
    Highland is a commuter rail station on the Needham Line serving passengers in the Boston, Massachusetts area.
  • C. Highland
    Highland is a city in Utah County, Utah, known as a suburban residential community in the Provo–Orem metropolitan area.
  • D. 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.
  • E. Highland
    Highland is the historic Virginia plantation estate that served as the home of U.S. President James Monroe.
  • 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_69e11e3c4c5c81908d336165816b12e0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a2f2f90819080b5bb73a6052c24 completed April 28, 2026, 9:44 p.m.
Created at: April 16, 2026, 8:34 p.m.