Triple

T13799320
Position Surface form Disambiguated ID Type / Status
Subject Lake Vänern E331596 entity
Predicate hasCityOnShore P969 FINISHED
Object Lidköping E360442 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: Lidköping | Statement: [Lake Vänern, hasCityOnShore, Lidköping]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lidköping
Context triple: [Lake Vänern, hasCityOnShore, Lidköping]
  • A. Lidköping chosen
    Lidköping is a Swedish town on the southern shore of Lake Vänern known for its historic center, ceramics industry, and role as a local commercial hub.
  • B. Norrköping
    Norrköping is a historic industrial city in eastern Sweden known for its preserved textile mills, waterways, and cultural institutions.
  • C. Nyköping
    Nyköping is a historic coastal town in southeastern Sweden known for its medieval castle, harbor, and role as a regional administrative and cultural center.
  • D. Sundsvall
    Sundsvall is a coastal city in central Sweden known as an important industrial and commercial center on the Gulf of Bothnia.
  • E. Linköping
    Linköping is a major city in southern Sweden known for its university, high-tech industry, and historic cathedral.
  • 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_69d81c58feb08190a77bca8bf7d6d20f completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de025ce9148190b23370f6a522ff7a completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe0cce10c88190bf25404fc4c75bbf completed May 8, 2026, 4:18 p.m.
Created at: April 9, 2026, 10:11 p.m.