Triple
T4240418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Mälaren |
E95397
|
entity |
| Predicate | hasCityOnShore |
P969
|
FINISHED |
| Object | Strängnäs |
E176028
|
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: Strängnäs | Statement: [Lake Mälaren, hasCityOnShore, Strängnäs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Strängnäs Context triple: [Lake Mälaren, hasCityOnShore, Strängnäs]
-
A.
Strängnäs
chosen
Strängnäs is a historic Swedish town known for its medieval cathedral and picturesque location on the shores of Lake Mälaren.
-
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.
Mönsterås
Mönsterås is a small coastal town and municipality in Kalmar County, southeastern Sweden, known for its Baltic Sea shoreline and traditional Swedish countryside.
-
D.
Bollstanäs
Bollstanäs is a residential locality in Sweden situated within the suburban area of Upplands Väsby, north of Stockholm.
-
E.
Hjulsta
Hjulsta is a suburb in northwestern Stockholm, Sweden, known for being the terminus of one of the Stockholm metro lines.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e77fb5c8190b298818acb68ff63 |
completed | March 12, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5a86fe7708190a64ba187fb302c9a |
completed | March 14, 2026, 6:26 p.m. |
Created at: March 12, 2026, 11:05 p.m.