Triple

T4873561
Position Surface form Disambiguated ID Type / Status
Subject Numedal E109143 entity
Predicate hasNearbyCity P350 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: [Numedal, hasNearbyCity, Kongsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kongsberg
Context triple: [Numedal, hasNearbyCity, 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_69bd440d96a48190b0c87069adef2af1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d9fa0b08190ab1fc7ec395dca37 completed March 20, 2026, 3:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69be6fb5da2c8190aeec7d6d11b12b11 completed March 21, 2026, 10:15 a.m.
Created at: March 20, 2026, 1:27 p.m.