Triple
T2877739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lübeck |
E56916
|
entity |
| Predicate | twinCity |
P1072
|
FINISHED |
| Object | Kotka |
E285670
|
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: Kotka | Statement: [Lübeck, twinCity, Kotka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kotka Context triple: [Lübeck, twinCity, Kotka]
-
A.
Kotka
chosen
Kotka is a coastal city in southeastern Finland on the Gulf of Finland, known as an important port and maritime center.
-
B.
Pori
Pori is a coastal city in western Finland known for its industrial heritage, port, and annual Pori Jazz Festival.
-
C.
Vaasa
Vaasa is a coastal city in western Finland known for its maritime heritage, bilingual Finnish-Swedish culture, and role as a regional economic and educational center.
-
D.
Pirkkala
Pirkkala is a municipality in the Pirkanmaa region of southern Finland, located near the city of Tampere and known for its growing residential areas and proximity to Tampere-Pirkkala Airport.
-
E.
Kokkola
Kokkola is a coastal city in western Finland known for its maritime heritage and role as a military and naval 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe007329c8190b0bc1851c7307124 |
completed | March 7, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b53fc6f4b48190aebcf7457b6d670d |
completed | March 14, 2026, 11 a.m. |
Created at: March 6, 2026, 10:03 p.m.