Triple

T15040392
Position Surface form Disambiguated ID Type / Status
Subject Söderort E378584 entity
Predicate hasPart P35 FINISHED
Object Skärholmen E378324 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: Skärholmen | Statement: [Söderort, hasPart, Skärholmen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skärholmen
Context triple: [Söderort, hasPart, Skärholmen]
  • A. Skärholmen chosen
    Skärholmen is a suburban district in southwestern Stockholm, Sweden, known for its large shopping center and residential areas.
  • B. Munkholmen
    Munkholmen is a small historic island off Trondheim, Norway, known for its past roles as a monastery, fortress, prison, and World War II defensive site, and today as a popular tourist destination.
  • C. Kastellholmen
    Kastellholmen is a small island in central Stockholm, Sweden, known for its historic red-brick citadel and scenic waterfront views.
  • D. Skarpö
    Skarpö is an island in the Stockholm archipelago of Sweden, situated within Vaxholm Municipality and known for its coastal scenery and residential character.
  • E. Storholmen
    Storholmen is an island located in Lake Femunden, one of Norway’s largest inland lakes.
  • 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_69d85cd46b2c819090d054c27787f677 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded82e79a481908ddb9609af8c4407 completed April 15, 2026, 12:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe9de388508190bb0ecc04740cbe15 completed May 9, 2026, 2:37 a.m.
Created at: April 10, 2026, 3 a.m.