Triple
T9275353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalmar War |
E222932
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Kalmar |
E161776
|
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: Kalmar | Statement: [Kalmar War, location, Kalmar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kalmar Context triple: [Kalmar War, location, Kalmar]
-
A.
Kalmar
chosen
Kalmar is a historic coastal city in southeastern Sweden known for its medieval castle, role in the Kalmar Union, and connection to the island of Öland.
-
B.
Karlskrona
Karlskrona is a historic Swedish coastal city and naval base known for its well-preserved maritime architecture and UNESCO-listed naval port.
-
C.
Kristianstad
Kristianstad is a historic city in southern Sweden known for its well-preserved Renaissance architecture and proximity to the wetlands of the Kristianstad Vattenrike Biosphere Reserve.
-
D.
Halmstad
Halmstad is a coastal city in southwestern Sweden known for its historic town center, harbor, and role as a strategic site in Scandinavian conflicts.
-
E.
Karlshamn
Karlshamn is a coastal town in southern Sweden known for its harbor, archipelago, and role as a regional industrial and transport hub.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd078a045c8190b2c4d1ec64b932ad |
completed | April 1, 2026, 11:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0f38f99b88190bb979bf9255c07d7 |
completed | April 4, 2026, 11:18 a.m. |
Created at: March 30, 2026, 7:34 p.m.