Triple

T915798
Position Surface form Disambiguated ID Type / Status
Subject Tbilisi E19766 entity
Predicate hasEthnicGroup P1898 FINISHED
Object Russians E18323 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: Russians | Statement: [Tbilisi, hasEthnicGroup, Russians]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Russians
Context triple: [Tbilisi, hasEthnicGroup, Russians]
  • A. Russians chosen
    Russians are an East Slavic ethnic group primarily associated with Russia, its language, and its cultural and historical traditions.
  • B. Russin
    Russin is a small wine-producing municipality and village located in the canton of Geneva in southwestern Switzerland.
  • C. Ukrainians
    Ukrainians are an East Slavic ethnic group native to Ukraine, characterized by their own language, culture, and national identity.
  • D. Rusyns
    Rusyns are an East Slavic ethnic group traditionally inhabiting the Carpathian Mountain region, with their own distinct language, culture, and historical identity separate from but closely related to Ukrainians.
  • E. Tatars
    Tatars are a Turkic ethnic group historically centered in regions of Russia and Central Asia, known for their diverse subgroups, Islamic heritage, and significant cultural influence across the Eurasian steppe.
  • 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_69a4939f91a08190ba68c2c81eab90fe completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b2f789108190815fd1efbd6cc24f completed March 1, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7ee074e9481908430b61d0ac73f4f completed March 4, 2026, 8:32 a.m.
Created at: March 1, 2026, 7:39 p.m.