Triple

T4434641
Position Surface form Disambiguated ID Type / Status
Subject Buskerud E95618 entity
Predicate borders P224 FINISHED
Object Akershus E92851 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: Akershus | Statement: [Buskerud, borders, Akershus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akershus
Context triple: [Buskerud, borders, Akershus]
  • A. Akershus chosen
    Akershus is a historical county in southeastern Norway that encompassed areas around the capital Oslo and played a key role in the region’s administrative and military history.
  • B. Akershus Fortress
    Akershus Fortress is a historic medieval castle and former royal residence that has served as a key military stronghold and national symbol in Norway’s capital.
  • C. Eidsvoll
    Eidsvoll is a historic Norwegian town best known as the site where Norway’s constitution was drafted and signed in 1814.
  • D. Royal Palace, Oslo
    The Royal Palace in Oslo is the official residence of the Norwegian monarch and a central symbol of Norway’s constitutional monarchy and national heritage.
  • E. Kolsås
    Kolsås is a suburban area in Bærum, Norway, known as the endpoint of one of the Oslo Metro lines and for its nearby forested hill popular for hiking and climbing.
  • 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_69b3453ea2b48190a26f154b3b8fece5 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35588e99881908fea7b71a33e2bb6 completed March 13, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69b6137378dc8190900c8fda2693c4da completed March 15, 2026, 2:03 a.m.
Created at: March 12, 2026, 11:31 p.m.