Triple

T15782674
Position Surface form Disambiguated ID Type / Status
Subject Liljeholmsbron E382657 entity
Predicate namedAfter P63 FINISHED
Object Liljeholmen E1141440 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: Liljeholmen | Statement: [Liljeholmsbron, namedAfter, Liljeholmen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Liljeholmen
Context triple: [Liljeholmsbron, namedAfter, Liljeholmen]
  • A. Liljeholmen chosen
    Liljeholmen is a district in southern Stockholm, Sweden, known for its waterfront location, residential areas, and commercial centers.
  • B. Blasieholmen
    Blasieholmen is a central Stockholm peninsula known for its historic buildings, cultural institutions, and waterfront views across from the Old Town.
  • C. Helgeandsholmen
    Helgeandsholmen is a small central Stockholm islet best known as the site of the Swedish Parliament building and part of the historic city core.
  • D. Thurø
    Thurø is a small Danish island in the Baltic Sea known for its coastal scenery, beaches, and traditional maritime village atmosphere.
  • E. Heggholmen
    Heggholmen is a small island in the Oslofjord near Oslo, Norway, known for its coastal scenery and proximity to other islets like Gressholmen.
  • 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_69d86da16e188190b89af699f1ed0bfe completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e05400716881909bc43212c8ea54d5 completed April 16, 2026, 3:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffcf0dd5ec8190b9a44d2ccbe90c52 completed May 10, 2026, 12:19 a.m.
Created at: April 10, 2026, 4:48 a.m.