Triple

T20319259
Position Surface form Disambiguated ID Type / Status
Subject RIX E492163 entity
Predicate timeZone P109 FINISHED
Object Europe/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: Europe/Riga | Statement: [RIX, timeZone, Europe/Riga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Europe/Riga
Context triple: [RIX, timeZone, Europe/Riga]
  • A. Riga Planning Region
    Riga Planning Region is an administrative planning area in Latvia that encompasses the capital city of Riga and its surrounding municipalities for regional development and coordination.
  • B. 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.
  • C. Riga
    Riga is a town in the Sitamarhi district of the Indian state of Bihar.
  • D. 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.
  • E. Aizkraukle, Latvia
    Aizkraukle is a small town in central Latvia on the right bank of the Daugava River, known as a regional administrative center and former Soviet-era hydroelectric power plant settlement.
  • 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_69e0b4a0134081909113563e1c3ba68a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6778abd14819098a01fd32217fdde completed April 20, 2026, 6:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a086126c9a08190a6dcb30d118a2730 completed May 16, 2026, 12:20 p.m.
Created at: April 16, 2026, 11:20 a.m.