Triple

T4365551
Position Surface form Disambiguated ID Type / Status
Subject Oppland E98763 entity
Predicate borderedBy 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: [Oppland, borderedBy, Akershus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akershus
Context triple: [Oppland, borderedBy, 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_69b3454c772081908e20173e379e8ebe completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35200263081909bb326a4d7a8db99 completed March 12, 2026, 11:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5dbcbbd1881908eb9f0ea6b2fe16b completed March 14, 2026, 10:06 p.m.
Created at: March 12, 2026, 11:17 p.m.