Triple

T20135887
Position Surface form Disambiguated ID Type / Status
Subject Red line (Stockholm metro) E491023 entity
Predicate passesThroughStation P3947 FINISHED
Object Hornstull NE NERFINISHED

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: Hornstull | Statement: [Red line (Stockholm metro), passesThroughStation, Hornstull]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hornstull
Context triple: [Red line (Stockholm metro), passesThroughStation, Hornstull]
  • A. Hornstull chosen
    Hornstull is a vibrant waterfront neighborhood on the western edge of Södermalm in central Stockholm, known for its bars, restaurants, and cultural venues.
  • B. Hystad
    Hystad is a residential area and neighboring settlement to Leirvik in the municipality of Stord in western Norway.
  • C. Hjulsta
    Hjulsta is a suburb in northwestern Stockholm, Sweden, known for being the terminus of one of the Stockholm metro lines.
  • D. Gangstad
    Gangstad is a small settlement located within the municipality of Inderøy in Trøndelag county, Norway.
  • E. Stenstaden
    Stenstaden is the historic stone-built city center of Sundsvall, Sweden, known for its ornate late 19th-century architecture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da62651a0c8190a3e05e95e056a66b completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66766e46c81908721fd47066dc9f8 completed April 20, 2026, 5:50 p.m.
Created at: April 11, 2026, 11:32 p.m.