Triple
T9274611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Estonia |
E222913
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Võru |
E367591
|
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: Võru | Statement: [Southern Estonia, hasCity, Võru]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Võru Context triple: [Southern Estonia, hasCity, Võru]
-
A.
Viljandi
Viljandi is a historic town in southern Estonia known for its medieval castle ruins, rich cultural life, and annual folk music festival.
-
B.
Kuressaare
Kuressaare is the main town on Estonia’s Saaremaa island, known for its well-preserved medieval castle and seaside spa resort atmosphere.
-
C.
Võru County
chosen
Võru County is a rural region in southeastern Estonia known for its distinct South Estonian (Võro) linguistic and cultural heritage.
-
D.
Pärnamäe
Pärnamäe is a village located in Viimsi Parish in northern Estonia, near the capital city Tallinn.
-
E.
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.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd078a045c8190b2c4d1ec64b932ad |
completed | April 1, 2026, 11:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09c3dd140819099fc0e95c4d48ba9 |
completed | April 4, 2026, 5:06 a.m. |
Created at: March 30, 2026, 7:33 p.m.