Triple
T14237891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borås |
E352932
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Mikkeli |
—
|
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: Mikkeli | Statement: [Borås, hasTwinTown, Mikkeli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikkeli Context triple: [Borås, hasTwinTown, Mikkeli]
-
A.
Mikkeli
chosen
Mikkeli is a city in eastern Finland known as an important regional center in the Finnish Lakeland area, noted for its lakeside scenery and historical significance.
-
B.
Riihimäki
Riihimäki is a Finnish town known as a regional railway hub and industrial center located north of Helsinki.
-
C.
Kuokkala
Kuokkala is a former Finnish locality on the Karelian Isthmus, now known as Repino in Saint Petersburg, Russia.
-
D.
Kuokkala
Kuokkala is a residential district of the city of Jyväskylä in central Finland, known for its lakeside location and distinctive bridge connection to the city center.
-
E.
Imatra
Imatra is a town and municipality in southeastern Finland known for its industrial history, proximity to the Russian border, and the Imatrankoski rapids.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62422e28819089e7115052a28c96 |
completed | April 14, 2026, 3:50 p.m. |
Created at: April 10, 2026, 1:08 a.m.