Triple

T11098477
Position Surface form Disambiguated ID Type / Status
Subject Feliks E262438 entity
Predicate hasLanguageOfUse P207 FINISHED
Object Latvian E168863 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: Latvian | Statement: [Feliks, hasLanguageOfUse, Latvian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Latvian
Context triple: [Feliks, hasLanguageOfUse, Latvian]
  • 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. Latvians
    Latvians are a Baltic ethnic group native to Latvia, known for their distinct Latvian language, rich folk traditions, and cultural heritage along the eastern coast of the Baltic Sea.
  • D. Latn
    Latn is the ISO 15924 script code representing the Latin alphabet used for writing numerous modern languages worldwide.
  • E. Lithuanian
    Lithuanian is a Baltic language spoken primarily in Lithuania and known for preserving many archaic features of Proto-Indo-European.
  • 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_69d6aa9a40d88190a373e2c7e48285db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79a0b2890819081c4efc50e995cdd completed April 9, 2026, 12:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3e7eca9bc8190b43bae081d97d804 completed April 18, 2026, 8:22 p.m.
Created at: April 8, 2026, 9:27 p.m.