Triple
T14531710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rögle BK |
E340930
|
entity |
| Predicate | homeCity |
P263
|
FINISHED |
| Object | Ängelholm |
E122152
|
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: Ängelholm | Statement: [Rögle BK, homeCity, Ängelholm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ängelholm Context triple: [Rögle BK, homeCity, Ängelholm]
-
A.
Ängelholm
chosen
Ängelholm is a coastal town in southern Sweden known for its sandy beaches, aviation museum, and scenic location at the mouth of the Rönne River.
-
B.
Karlshamn
Karlshamn is a coastal town in southern Sweden known for its harbor, archipelago, and role as a regional industrial and transport hub.
-
C.
Oskarshamn
Oskarshamn is a coastal town in southeastern Sweden known for its Baltic Sea harbor and proximity to the island of Gotland.
-
D.
Strängnäs
Strängnäs is a historic Swedish town known for its medieval cathedral and picturesque location on the shores of Lake Mälaren.
-
E.
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.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea052d01c81909c8592c351be6f35 |
completed | April 14, 2026, 8:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd8ab24f8c8190bb0e68ebb854844d |
completed | May 8, 2026, 7:03 a.m. |
Created at: April 10, 2026, 1:22 a.m.