Triple
T1024296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonia |
E22105
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Tallinn |
E20558
|
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: Tallinn | Statement: [Estonia, capital, Tallinn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tallinn Context triple: [Estonia, capital, Tallinn]
-
A.
Tallinn
chosen
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.
-
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.
Helsinki
Helsinki is the capital and largest city of Finland, known for its coastal location on the Baltic Sea, modern design, and vibrant cultural life.
-
D.
Riga
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.
-
E.
Turku
Turku is one of Finland’s oldest and historically most important cities, located on the southwest coast and known for its medieval heritage and major Baltic Sea port.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7e28df08190b5be7794442a6f21 |
completed | March 1, 2026, 10:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac5381e020819094e02c3d20acab95 |
completed | March 7, 2026, 4:34 p.m. |
Created at: March 1, 2026, 7:41 p.m.