Triple
T21703429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohuslän |
E535711
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Kungälv |
—
|
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: Kungälv | Statement: [Bohuslän, containsCity, Kungälv]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kungälv Context triple: [Bohuslän, containsCity, Kungälv]
-
A.
Kungälv
chosen
Kungälv is a town in western Sweden known for the historic Bohus Fortress and its location near the Göta älv north of Gothenburg.
-
B.
Älvsjö
Älvsjö is a suburban district in southern Stockholm, Sweden, known for its residential areas and the Stockholm International Fairs exhibition center.
-
C.
Mölndalsån
Mölndalsån is a river in western Sweden that flows through the city of Mölndal toward Gothenburg, historically important for local industry and milling.
-
D.
Trollbäcken
Trollbäcken is a residential suburban district in the Stockholm County area of Sweden, known for its proximity to lakes and green spaces.
-
E.
Hovsjö
Hovsjö is a residential district in the city of Södertälje, Sweden, known for its large-scale housing estates and diverse population.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b82901c81909de242c920fbc164 |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 16, 2026, 6:46 p.m.