Triple
T9562089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metsakalmistu cemetery |
E230698
|
entity |
| Predicate | ownedBy |
P347
|
FINISHED |
| Object | City of 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: City of Tallinn | Statement: [Metsakalmistu cemetery, ownedBy, City of Tallinn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Tallinn Context triple: [Metsakalmistu cemetery, ownedBy, City of 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.
Maardu
Maardu is an industrial town in northern Estonia, located just east of the capital Tallinn in Harju County.
-
D.
Vasai
Vasai is a historic coastal town in western India, near Mumbai, known for its strategic importance under Portuguese and later British rule and as the site of the 1802 Treaty of Bassein.
-
E.
Riga
Riga is a town in the Sitamarhi district of the Indian state of Bihar.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994d31e08190b139f5ad10d8ea31 |
completed | April 1, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d20cbe7fb88190a945870540d4c973 |
completed | April 5, 2026, 7:18 a.m. |
Created at: March 30, 2026, 8:03 p.m.