Triple
T15040731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skanstull |
E378591
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Årsta |
E1137247
|
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: Årsta | Statement: [Skanstull, near, Årsta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Årsta Context triple: [Skanstull, near, Årsta]
-
A.
Årsta
chosen
Årsta is a residential district in southern Stockholm, Sweden, known for its mid-20th-century architecture and proximity to both the city center and green recreational areas.
-
B.
Åsta
Åsta is a river in southeastern Norway that serves as a notable tributary to the country’s longest river, the Glomma.
-
C.
Åre
Åre is a well-known ski resort village in northern Sweden, recognized for its alpine skiing and winter sports tourism.
-
D.
Bollstanäs
Bollstanäs is a residential locality in Sweden situated within the suburban area of Upplands Väsby, north of Stockholm.
-
E.
Kårsta
Kårsta is a locality in Vallentuna Municipality, Sweden, known as the northern terminus of Stockholm’s Roslagsbanan narrow-gauge railway line.
- 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_69fed31debb48190908d59178e67adb6 |
completed | May 9, 2026, 6:24 a.m. |
Created at: April 10, 2026, 3 a.m.