Triple

T6417393
Position Surface form Disambiguated ID Type / Status
Subject Birsay Hills E127863 entity
Predicate near P350 FINISHED
Object Birsay E123294 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: Birsay | Statement: [Birsay Hills, near, Birsay]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Birsay
Context triple: [Birsay Hills, near, Birsay]
  • A. Birsay chosen
    Birsay is a coastal parish and village area on the northwest of Orkney Mainland in Scotland, known for its rich Norse history and archaeological sites.
  • B. Buhera
    Buhera is a rural town and district center in eastern Zimbabwe known for its agricultural activities and location within Manicaland Province.
  • C. Biram
    Biram is an ancient Hausa city in northern Nigeria traditionally regarded as one of the original Hausa city-states (Hausa Bakwai) and an early center of Hausa culture and authority.
  • D. Takelsa
    Takelsa is a coastal town in northeastern Tunisia known for its agriculture and location within the Nabeul region on the Cap Bon peninsula.
  • E. Bisha
    Bisha is a major inland city in southwestern Saudi Arabia known for its agricultural production and strategic location within the Asir region.
  • 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_69c0083815208190a9b299b8e0640218 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c068ea06b08190901e0c0a18fd5170 completed March 22, 2026, 10:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69c640ce3f9481908fa96fb5b2bc8db9 completed March 27, 2026, 8:33 a.m.
Created at: March 22, 2026, 4:42 p.m.