Triple
T15073415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stureplan |
E379937
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Birger Jarlsgatan |
E386915
|
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: Birger Jarlsgatan | Statement: [Stureplan, locatedOn, Birger Jarlsgatan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Birger Jarlsgatan Context triple: [Stureplan, locatedOn, Birger Jarlsgatan]
-
A.
Birger Jarlsgatan
chosen
Birger Jarlsgatan is a major central street in Stockholm, Sweden, known for its upscale shops, offices, and role as a key thoroughfare through the Östermalm district.
-
B.
Nybrogatan
Nybrogatan is a prominent street in Stockholm’s upscale Östermalm district, known for its boutiques, restaurants, and vibrant city life.
-
C.
Kungsholmsgatan
Kungsholmsgatan is a street in central Stockholm, Sweden, located on the island of Kungsholmen.
-
D.
Sankt Eriksgatan
Sankt Eriksgatan is a major street in central Stockholm, Sweden, known for its shops, restaurants, and role as a key traffic artery through the city.
-
E.
Sturegatan
Sturegatan is a central street in Stockholm, Sweden, known for its proximity to Humlegården park and its mix of offices, shops, and restaurants.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fa0570819088a97b28173154cd |
completed | April 15, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1a61136081908198806944c81808 |
completed | May 9, 2026, 11:28 a.m. |
Created at: April 10, 2026, 3:02 a.m.