Triple
T3676372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm metro |
E78001
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Fridhemsplan |
E310303
|
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: Fridhemsplan | Statement: [Stockholm metro, hasStation, Fridhemsplan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fridhemsplan Context triple: [Stockholm metro, hasStation, Fridhemsplan]
-
A.
Fridhemsplan
chosen
Fridhemsplan is a major public square and transport hub in central Stockholm, known for its busy metro interchange and surrounding commercial area.
-
B.
Youngstorget
Youngstorget is a central public square in Oslo, Norway, known as a historic hub for political rallies, labor movement events, and urban social life.
-
C.
Hötorget
Hötorget is a central square in downtown Stockholm known for its market stalls, surrounding shops, and cultural venues.
-
D.
Slussen
Slussen is a major transport hub and metro station in central Stockholm, serving as a key interchange between multiple subway lines and other public transit.
-
E.
Sergels torg
Sergels torg is a central public square and major meeting point in downtown Stockholm, known for its modernist design and iconic glass obelisk.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc462ffdc8190896e9f98f648e2f3 |
completed | March 8, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4cde628c08190adc058d8d35a5e5d |
completed | March 14, 2026, 2:54 a.m. |
Created at: March 8, 2026, 3:25 p.m.