Triple
T20791229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roslagsbanan |
E511781
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Kårsta |
—
|
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: Kårsta | Statement: [Roslagsbanan, terminus, Kårsta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kårsta Context triple: [Roslagsbanan, terminus, Kårsta]
-
A.
Kårsta
chosen
Kårsta is a locality in Vallentuna Municipality, Sweden, known as the northern terminus of Stockholm’s Roslagsbanan narrow-gauge railway line.
-
B.
Hjulsta
Hjulsta is a suburb in northwestern Stockholm, Sweden, known for being the terminus of one of the Stockholm metro lines.
-
C.
Kungsbacka
Kungsbacka is a town in southwestern Sweden known for its coastal location, historic wooden center, and role as a commuter hub for nearby Gothenburg.
-
D.
Strömstad
Strömstad is a coastal town and municipality in western Sweden, near the Norwegian border, known for its archipelago, tourism, and ferry connections.
-
E.
Eidskog
Eidskog is a rural municipality in Innlandet county, Norway, known for its forests, lakes, and location along the Swedish border.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c29010508190bf2cf577d7f64754 |
completed | April 21, 2026, 12:19 a.m. |
Created at: April 16, 2026, 12:38 p.m.