Triple

T5152315
Position Surface form Disambiguated ID Type / Status
Subject Porsgrunn E116224 entity
Predicate locatedNear P294 FINISHED
Object Larvik E149637 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: Larvik | Statement: [Porsgrunn, locatedNear, Larvik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Larvik
Context triple: [Porsgrunn, locatedNear, Larvik]
  • A. Larvik chosen
    Larvik is a coastal town and municipality in Vestfold, Norway, known for its harbor, beaches, and historic connections to the shipping and timber industries.
  • B. Levanger
    Levanger is a historic town and municipality in Trøndelag county, Norway, known for its traditional wooden architecture and role as a regional commercial and educational center.
  • C. Lørenskog
    Lørenskog is a suburban municipality in Viken county, Norway, located just east of Oslo and known for its residential areas and commercial centers.
  • D. Ørsta
    Ørsta is a municipality in Møre og Romsdal county, Norway, known for its dramatic fjord and mountain landscapes and as a center for outdoor activities like hiking and skiing.
  • E. 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.
  • 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_69bd445d94788190b72e2cc563120995 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd78daab708190a42734a14dddb2fc completed March 20, 2026, 4:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69bfb1324c2c8190ba2a1c5708ba88e5 completed March 22, 2026, 9:06 a.m.
Created at: March 20, 2026, 1:44 p.m.