Triple

T13171279
Position Surface form Disambiguated ID Type / Status
Subject Stora Essingen E312980 entity
Predicate connectedTo P37 FINISHED
Object Lilla Essingen E310297 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: Lilla Essingen | Statement: [Stora Essingen, connectedTo, Lilla Essingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lilla Essingen
Context triple: [Stora Essingen, connectedTo, Lilla Essingen]
  • A. Lilla Essingen chosen
    Lilla Essingen is a small island and residential district in central Stockholm, known for its waterfront apartments and proximity to the city center.
  • B. Stora Essingen
    Stora Essingen is an island and residential district in central Stockholm, Sweden, known for its waterfront housing and connections via the Essingeleden motorway.
  • C. Lindesberg
    Lindesberg is a small historic town in central Sweden known for its mining heritage and lakeside setting.
  • D. Bollstanäs
    Bollstanäs is a residential locality in Sweden situated within the suburban area of Upplands Väsby, north of Stockholm.
  • E. Nässjö
    Nässjö is a small Swedish town in Jönköping County known as a regional railway hub and service center in southern Sweden.
  • 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_69d806ac3ee081909b2fd27d060aa974 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c2f22b881908a0af3af0a0af971 completed April 10, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f70a2a3f2881909af3e146ee24062d completed May 3, 2026, 8:41 a.m.
Created at: April 9, 2026, 9:13 p.m.