Triple

T4206528
Position Surface form Disambiguated ID Type / Status
Subject Viken E93795 entity
Predicate contains P35 FINISHED
Object Kongsberg E102940 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: Kongsberg | Statement: [Viken, contains, Kongsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kongsberg
Context triple: [Viken, contains, Kongsberg]
  • A. Kongsberg chosen
    Kongsberg is a Norwegian town known for its historic silver mines and its modern high-tech and defense industries.
  • B. Porsgrunn
    Porsgrunn is an industrial and port city in Telemark county in southeastern Norway, known for its porcelain production and location along the Telemark Canal.
  • C. Notodden
    Notodden is a town and municipality in Vestfold og Telemark county, Norway, known for its industrial heritage and annual blues festival.
  • D. Skien
    Skien is a historic city in southern Norway known as the birthplace of playwright Henrik Ibsen and as a regional commercial and industrial center.
  • E. Steinkjer
    Steinkjer is a town and municipality in central Norway that serves as an important regional center and administrative hub in Trøndelag 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_69b3451743608190808f41d17ccf2650 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b3480cfacc81909a2705eb4e9ce8c1 completed March 12, 2026, 11:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69b596258db88190aed602eeb2323fee completed March 14, 2026, 5:08 p.m.
Created at: March 12, 2026, 11:03 p.m.