Triple
T21807792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Högsby Municipality |
E538391
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Högsby |
—
|
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: Högsby | Statement: [Högsby Municipality, hasSettlement, Högsby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Högsby Context triple: [Högsby Municipality, hasSettlement, Högsby]
-
A.
Högsby
chosen
Högsby is a small locality in Kalmar County, Sweden, known primarily as the seat of Högsby Municipality.
-
B.
Stureby
Stureby is a residential district in southern Stockholm, Sweden, known for its suburban character and local amenities.
-
C.
Ljungby
Ljungby is a small Swedish town in southern Småland known for its lakeside surroundings, forestry-based economy, and role as a local commercial and cultural center.
-
D.
Melmerby
Melmerby is a small rural village located in the Coverdale area of the Yorkshire Dales in North Yorkshire, England.
-
E.
Mjölby
Mjölby is a small Swedish town known for its agricultural surroundings and location in the southern part of Östergötland County.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f078047ca88190a0efa4bc7f2faf80 |
completed | April 28, 2026, 9:04 a.m. |
Created at: April 16, 2026, 6:53 p.m.