Triple
T726745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Riga |
E14742
|
entity |
| Predicate | signedIn |
P441
|
FINISHED |
| Object | Riga |
E20805
|
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: Riga | Statement: [Treaty of Riga, signedIn, Riga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riga Context triple: [Treaty of Riga, signedIn, Riga]
-
A.
Riga
chosen
Riga is the capital and largest city of Latvia, a historic cultural and economic hub on the Baltic Sea known for its Art Nouveau architecture and significant port.
-
B.
Tallinn
Tallinn is the capital and largest city of Estonia, a historic Baltic Sea port known for its well-preserved medieval Old Town and strategic maritime location.
-
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.
Kaunas
Kaunas is the second-largest city in Lithuania, known as a historic cultural and academic center located at the confluence of the Nemunas and Neris rivers.
-
E.
Rostock
Rostock is a historic Hanseatic city in northern Germany known for its significant seaport on the Baltic Sea and its long maritime and trading tradition.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5a9adf08190bf2baade7e2e1c1c |
completed | March 1, 2026, 8:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a66d936bbc81908708ee5d0fc82100 |
completed | March 3, 2026, 5:11 a.m. |
Created at: March 1, 2026, 7:37 p.m.