Triple

T20319341
Position Surface form Disambiguated ID Type / Status
Subject Spilve Airport E492166 entity
Predicate locatedIn P40 FINISHED
Object Riga Municipality NE NERFINISHED

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 Municipality | Statement: [Spilve Airport, locatedIn, Riga Municipality]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Riga Municipality
Context triple: [Spilve Airport, locatedIn, Riga Municipality]
  • A. Riga Municipality chosen
    Riga Municipality is the local government area encompassing Latvia’s capital city, Riga, and its surrounding administrative territory.
  • B. Riga City Council
    Riga City Council is the elected municipal governing body responsible for administering and making policy decisions for Latvia’s capital city, Riga.
  • C. 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.
  • D. Riga Central District
    Riga Central District is a central administrative area of Riga, Latvia, encompassing key urban streets, commercial zones, and cultural landmarks.
  • 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 (2 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.
Created at: April 16, 2026, 11:20 a.m.