Triple

T15751670
Position Surface form Disambiguated ID Type / Status
Subject Tromsø amt E381860 entity
Predicate borders P224 FINISHED
Object Nordlands amt E401032 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: Nordlands amt | Statement: [Tromsø amt, borders, Nordlands amt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nordlands amt
Context triple: [Tromsø amt, borders, Nordlands amt]
  • A. Tromsø amt
    Tromsø amt was a former administrative county in northern Norway that historically encompassed the area later known as Troms.
  • B. Nordland county chosen
    Nordland county is a long, coastal region in northern Norway known for its dramatic fjords, islands, and Arctic landscapes.
  • C. Helgeland district
    Helgeland district is a traditional region in southern Nordland county, Norway, known for its coastal archipelagos, fjords, and scattered rural communities.
  • D. Romsdals amt
    Romsdals amt was a former county-level administrative division in Norway, historically located in the Romsdal region along the country’s western coast.
  • E. Stavanger amt
    Stavanger amt was a former administrative county in southwestern Norway that encompassed areas including Finnøy before later being reorganized into modern Rogaland county.
  • 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e05030e31081908c307a8dc7067db4 completed April 16, 2026, 2:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00dbf2567c81909ab6054ade27afac completed May 10, 2026, 7:26 p.m.
Created at: April 10, 2026, 4:47 a.m.