Triple
T2453261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Järvenpää |
E53754
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Pärnu |
E180225
|
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: Pärnu | Statement: [Järvenpää, hasTwinTown, Pärnu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pärnu Context triple: [Järvenpää, hasTwinTown, Pärnu]
-
A.
Pärnu
chosen
Pärnu is a coastal city in southwestern Estonia known as a popular summer resort and spa destination on the Baltic Sea.
-
B.
Tartu
Tartu is Estonia’s second-largest city and a historic cultural and intellectual center, best known as the country’s main university town.
-
C.
Viedma
Viedma is a city in northern Patagonia and one of the oldest settlements in Argentina, serving as the capital of Río Negro Province.
-
D.
Kuressaare
Kuressaare is the main town on Estonia’s Saaremaa island, known for its well-preserved medieval castle and seaside spa resort atmosphere.
-
E.
Viljandi
Viljandi is a historic town in southern Estonia known for its medieval castle ruins, rich cultural life, and annual folk music festival.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd0f699308190910a41520dc9efdb |
completed | March 7, 2026, 7:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afb6677ae0819099091bcf48328a69 |
completed | March 10, 2026, 6:12 a.m. |
Created at: March 6, 2026, 9:43 p.m.