Triple
T1837270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Army |
E41092
|
entity |
| Predicate | garrison |
P75
|
FINISHED |
| Object | Kungsängen |
E149968
|
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: Kungsängen | Statement: [Swedish Army, garrison, Kungsängen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kungsängen Context triple: [Swedish Army, garrison, Kungsängen]
-
A.
Kungsängen
chosen
Kungsängen is a locality in Stockholm County, Sweden, serving as the administrative and population center of Upplands-Bro Municipality.
-
B.
Skarpäng
Skarpäng is a residential urban area within Täby Municipality in Stockholm County, Sweden.
-
C.
Bollstanäs
Bollstanäs is a residential locality in Sweden situated within the suburban area of Upplands Väsby, north of Stockholm.
-
D.
Skogsön
Skogsön is an island in the Stockholm archipelago of Sweden, situated within Vaxholm Municipality and known for its natural coastal landscapes and holiday homes.
-
E.
Rosersberg
Rosersberg is a locality in Stockholm County, Sweden, known for its historic Rosersberg Palace and its location near Stockholm Arlanda Airport.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0380a4c81909a2ad0bfd97c884a |
completed | March 7, 2026, 4:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adc9b6dc9481908a83e60aee326bc4 |
completed | March 8, 2026, 7:10 p.m. |
Created at: March 4, 2026, 7:33 p.m.