Triple

T22671127
Position Surface form Disambiguated ID Type / Status
Subject Sudovian language E560218 entity
Predicate alternativeName P39 FINISHED
Object Yotvingian 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: Yotvingian language | Statement: [Sudovian language, alternativeName, Yotvingian language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yotvingian language
Context triple: [Sudovian language, alternativeName, Yotvingian language]
  • A. Yotvingian language chosen
    The Yotvingian language was an extinct Western Baltic language once spoken by the Yotvingian people in parts of what are now Poland, Lithuania, and Belarus.
  • B. Polabian language
    Polabian language was an extinct West Slavic language once spoken by the Polabian Slavs in what is now northeastern Germany.
  • C. Lombardic
    Lombardic is an extinct West Germanic language once spoken by the Lombards in parts of Italy during the early Middle Ages.
  • D. Alanic language
    The Alanic language was an extinct Eastern Iranian language once spoken by the Alans, an ancient nomadic people of the North Caucasus and Eurasian steppe.
  • E. Ripuarian
    Ripuarian is a group of closely related West Central German dialects spoken primarily in the Cologne region and surrounding areas along the Rhine.
  • 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.