Triple
T1559739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Riga |
E33290
|
entity |
| Predicate | locatedNearCity |
P3883
|
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: [Gulf of Riga, locatedNearCity, Pärnu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pärnu Context triple: [Gulf of Riga, locatedNearCity, 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.
Jelgava
Jelgava is a city in central Latvia known for its historic Jelgava Palace and role as a regional cultural and educational center.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90885d6208190b4b7d6ad336d4d16 |
completed | March 5, 2026, 4:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51ab8e208190b4bcf03e9a661070 |
completed | March 8, 2026, 10:38 a.m. |
Created at: March 4, 2026, 7:27 p.m.