Triple
T10568965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahrensburg |
E249427
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Viljandi |
E225374
|
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: Viljandi | Statement: [Ahrensburg, twinTown, Viljandi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Viljandi Context triple: [Ahrensburg, twinTown, Viljandi]
-
A.
Viljandi
chosen
Viljandi is a historic town in southern Estonia known for its medieval castle ruins, rich cultural life, and annual folk music festival.
-
B.
Jõgeva
Jõgeva is a small town in eastern Estonia known as a local administrative and cultural center and for recording some of the country’s lowest winter temperatures.
-
C.
Rieste
Rieste is a small municipality in Lower Saxony, Germany, situated within the Osnabrück district.
-
D.
Tartu
Tartu is Estonia’s second-largest city and a historic cultural and intellectual center, best known as the country’s main university town.
-
E.
Põlva
Põlva is a small town in southeastern Estonia known as a local administrative and cultural center surrounded by lakes and forested landscapes.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5272ff53c8190ae7c399d49b585f5 |
completed | April 7, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d96b5025b88190a078f5ad7b9cb3d5 |
completed | April 10, 2026, 9:27 p.m. |
Created at: April 6, 2026, 12:37 p.m.