Triple

T371969
Position Surface form Disambiguated ID Type / Status
Subject Eastern Europe E8286 entity
Predicate hasMajorCity P316 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: [Eastern Europe, hasMajorCity, Riga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riga
Context triple: [Eastern Europe, hasMajorCity, 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. Klaipėda
    Klaipėda is a Lithuanian port city on the Baltic Sea known as the country’s main maritime gateway and a key regional transport and industrial hub.
  • 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_69a2e7f2ec648190b42bc7db424f8109 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec00785481908551fc3571fcca47 completed Feb. 28, 2026, 1:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3fafb2df881909d5528acfb536ea8 completed March 1, 2026, 8:38 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.