Triple

T11609367
Position Surface form Disambiguated ID Type / Status
Subject Siege of Riga (1600–1601) E275342 entity
Predicate location P40 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: [Siege of Riga (1600–1601), location, Riga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riga
Context triple: [Siege of Riga (1600–1601), location, 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. Riga
    Riga is a town in the Sitamarhi district of the Indian state of Bihar.
  • C. Daugavpils
    Daugavpils is Latvia’s second-largest city, known as the birthplace of abstract expressionist painter Mark Rothko and for its multicultural heritage and 19th-century fortress.
  • D. Valmiera
    Valmiera is a historic city in northern Latvia, situated on the Gauja River and known today as a regional economic and cultural center in the Vidzeme region.
  • E. Liepāja, Latvia
    Liepāja is a major port city on Latvia’s Baltic Sea coast, known for its historic architecture, naval heritage, and cultural life.
  • 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_69d6aaf84b548190ac072e4fb89ae18f completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a04231d08190b8a07cd977d11ffa completed April 10, 2026, 7:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69e8a8311bcc8190a3fe7d28c593aea3 completed April 22, 2026, 10:51 a.m.
Created at: April 8, 2026, 9:38 p.m.