Triple
T15030188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-bana |
E378321
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Hjulsta |
E378961
|
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: Hjulsta | Statement: [T-bana, hasStation, Hjulsta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hjulsta Context triple: [T-bana, hasStation, Hjulsta]
-
A.
Hjulsta
chosen
Hjulsta is a suburb in northwestern Stockholm, Sweden, known for being the terminus of one of the Stockholm metro lines.
-
B.
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.
-
C.
Fagersta
Fagersta is an industrial town in central Sweden known for its steel production and manufacturing heritage.
-
D.
Hudiksvall
Hudiksvall is a coastal town in east-central Sweden known for its historic wooden buildings and harbor on the Gulf of Bothnia.
-
E.
Häggenås
Häggenås is a small locality in Jämtland County, northern Sweden, situated within Östersund Municipality.
- 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_69ded7e2416081908dfba48d7f7b4a84 |
completed | April 15, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa11f77788190866e0820d33af588 |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 10, 2026, 2:59 a.m.