Triple

T22671080
Position Surface form Disambiguated ID Type / Status
Subject Baltic languages E560217 entity
Predicate hasPart P35 FINISHED
Object Latvian language 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: Latvian language | Statement: [Baltic languages, hasPart, Latvian language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Latvian language
Context triple: [Baltic languages, hasPart, Latvian language]
  • A. Latvian chosen
    Latvian is a Baltic language spoken primarily in Latvia and one of the official languages of the European Union.
  • B. Latgalian
    Latgalian is an Eastern Baltic language variety closely related to Latvian, traditionally spoken by the Latgalian ethnic group in the Latgale region of eastern Latvia.
  • C. Latverian
    Latverian refers to something or someone from Latveria, the fictional Eastern European nation ruled by Doctor Doom in Marvel Comics.
  • D. Latuvi
    Latuvi is a small rural village in the Sierra Norte region of Oaxaca, Mexico, known for its mountainous landscapes and traditional indigenous culture.
  • E. Livonian language
    The Livonian language is an almost extinct Uralic language historically spoken by the Livonian people along the northern coast of Latvia.
  • 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_69e2454bfd00819099115715a22cb057 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1781f946c8190add74a7dac2b1819 completed April 29, 2026, 3:16 a.m.
Created at: April 17, 2026, 3:10 p.m.