Triple

T3458617
Position Surface form Disambiguated ID Type / Status
Subject Karelian language E72966 entity
Predicate closelyRelatedTo P37 FINISHED
Object Veps language E150709 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: Veps language | Statement: [Karelian language, closelyRelatedTo, Veps language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Veps language
Context triple: [Karelian language, closelyRelatedTo, Veps language]
  • A. Veps language chosen
    Veps language is a Finnic Uralic language spoken by the Veps people in northwestern Russia, closely related to Finnish and Karelian.
  • B. Votic language
    The Votic language is a nearly extinct Uralic language traditionally spoken by the Votes in Ingria, near the Gulf of Finland in northwestern Russia.
  • C. Evenki language
    The Evenki language is a Northern Tungusic language spoken by the Evenki people across Siberia, northeastern China, and Mongolia.
  • D. Karelian language
    The Karelian language is a Uralic language closely related to Finnish, traditionally spoken by the Karelian people in parts of Finland and northwestern Russia.
  • E. Erzya language
    The Erzya language is a Uralic, Finno-Volgaic language spoken primarily by the Erzya Mordvin people in central Russia.
  • 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_69ad85b12a908190a1d10a6b03b4f8ae completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbae4c18881908b48d16e46f78209 completed March 8, 2026, 6:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69b373aaff688190b9f12a7042055a1c completed March 13, 2026, 2:17 a.m.
Created at: March 8, 2026, 3:16 p.m.