Triple

T848335
Position Surface form Disambiguated ID Type / Status
Subject Southern Norway E18325 entity
Predicate contains P35 FINISHED
Object Tønsberg E112118 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: Tønsberg | Statement: [Southern Norway, contains, Tønsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tønsberg
Context triple: [Southern Norway, contains, Tønsberg]
  • A. Tønsberg chosen
    Tønsberg is a historic coastal town in southeastern Norway, often regarded as one of the country’s oldest cities and known for its Viking heritage and maritime culture.
  • B. Arendal
    Arendal is a coastal town and municipality in southern Norway known historically as a regional political and trading center.
  • C. Kristiansand
    Kristiansand is a coastal city in southern Norway known for its harbor, beaches, and role as a regional cultural and economic center.
  • D. Sandefjord
    Sandefjord is a coastal town and municipality in southern Norway known for its maritime heritage, whaling history, and popular seaside attractions.
  • E. Kolding
    Kolding is a historic Danish city in Southern Jutland known for Koldinghus Castle, its fjord-side location, and its role as a regional cultural and educational center.
  • 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_69a4938b04208190b82e1df6b572c548 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac1e41748190a21cd1ce5ebcb8ff completed March 1, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69aca2caba8c81908ef693677acbd4cc completed March 7, 2026, 10:12 p.m.
Created at: March 1, 2026, 7:38 p.m.