Triple
T11609465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truce of Altmark |
E275344
|
entity |
| Predicate | grantedControlOf |
P29286
|
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: [Truce of Altmark, grantedControlOf, Pärnu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pärnu Context triple: [Truce of Altmark, grantedControlOf, 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.
Maardu
Maardu is an industrial town in northern Estonia, located just east of the capital Tallinn in Harju County.
-
C.
Tartu
Tartu is Estonia’s second-largest city and a historic cultural and intellectual center, best known as the country’s main university town.
-
D.
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.
-
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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a04231d08190b8a07cd977d11ffa |
completed | April 10, 2026, 7:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a8311bcc8190a3fe7d28c593aea3 |
completed | April 22, 2026, 10:51 a.m. |
Created at: April 8, 2026, 9:38 p.m.