Triple
T15040683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zinkensdamm |
E378590
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Hornstull |
E378589
|
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: Hornstull | Statement: [Zinkensdamm, locatedNear, Hornstull]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hornstull Context triple: [Zinkensdamm, locatedNear, 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.
Hjulsta
Hjulsta is a suburb in northwestern Stockholm, Sweden, known for being the terminus of one of the Stockholm metro lines.
-
C.
Gangstad
Gangstad is a small settlement located within the municipality of Inderøy in Trøndelag county, Norway.
-
D.
Stenstaden
Stenstaden is the historic stone-built city center of Sundsvall, Sweden, known for its ornate late 19th-century architecture.
-
E.
Ballstad
Ballstad is a fishing village in Norway’s Lofoten archipelago, known for its scenic coastal landscape and traditional maritime culture.
- 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.