Triple
T7700657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viipuri |
E174484
|
entity |
| Predicate | hasNameInFinnish |
P23453
|
FINISHED |
| Object | Viipuri |
E174484
|
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: Viipuri | Statement: [Viipuri, hasNameInFinnish, Viipuri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viipuri Context triple: [Viipuri, hasNameInFinnish, Viipuri]
-
A.
Viipuri
chosen
Viipuri is the Finnish name for Vyborg, a historically significant city and former Finnish cultural center now located in Russia near the Finnish border.
-
B.
Pori
Pori is a coastal city in western Finland known for its industrial heritage, port, and annual Pori Jazz Festival.
-
C.
Nurmijärvi
Nurmijärvi is a municipality in southern Finland known for being one of the largest rural municipalities in the country and part of the Greater Helsinki region.
-
D.
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.
-
E.
Ruovesi
Ruovesi is a municipality in the Pirkanmaa region of Finland, known for its lakeside landscapes that have inspired Finnish artists and writers.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70288d02c819093d6f0e47707d0a3 |
completed | March 27, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c9bcbe7f488190aee034a51e8a281b |
completed | March 29, 2026, 11:58 p.m. |
Created at: March 27, 2026, 4:03 p.m.