Triple

T5734973
Position Surface form Disambiguated ID Type / Status
Subject Vårby E126479 entity
Predicate locatedNear P294 FINISHED
Object Lake Mälaren E95397 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: Lake Mälaren | Statement: [Vårby, locatedNear, Lake Mälaren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lake Mälaren
Context triple: [Vårby, locatedNear, Lake Mälaren]
  • A. Lake Mälaren chosen
    Lake Mälaren is a large freshwater lake in eastern Sweden that connects to the Baltic Sea and has Stockholm situated on its shores.
  • B. Lake Vättern
    Lake Vättern is Sweden’s second-largest lake, a deep, elongated freshwater body in south-central Sweden known for its clear waters and surrounding historic towns.
  • C. Lake Vänern
    Lake Vänern is Sweden’s largest lake and one of Europe’s biggest freshwater lakes, known for its extensive archipelagos and important role in regional ecology and transportation.
  • D. Lake Hjälmaren
    Lake Hjälmaren is one of Sweden’s largest lakes, located in central Sweden east of Lake Vänern and west of Stockholm.
  • E. Storsjön
    Storsjön is a large lake in central Sweden, famed for its scenic surroundings and the local legend of the lake monster Storsjöodjuret.
  • 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_69c0083082288190b7478cead6b5430a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02536706c8190a69665b75c8a38e9 completed March 22, 2026, 5:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c107d46ebc81908ec415782611ebef completed March 23, 2026, 9:28 a.m.
Created at: March 22, 2026, 3:47 p.m.