Triple

T13448204
Position Surface form Disambiguated ID Type / Status
Subject Pomor Russian E320539 entity
Predicate differsFrom P278 FINISHED
Object Standard Russian E715820 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: Standard Russian | Statement: [Pomor Russian, differsFrom, Standard Russian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Standard Russian
Context triple: [Pomor Russian, differsFrom, Standard Russian]
  • A. Russian language
    Russian is an East Slavic language spoken primarily in Russia and neighboring countries, serving as one of the world's major languages in politics, science, and culture.
  • B. Russan
    Russan is a commune in southern France situated along the Gardon River.
  • C. Russian chosen
    Russian is an East Slavic language that serves as the official language of Russia and a major lingua franca across much of Eastern Europe and Central Asia.
  • D. Russo
    Russo is an Italian surname commonly used as a variant of Rossi, often associated with people of Italian heritage.
  • E. Russin
    Russin is a small wine-producing municipality and village located in the canton of Geneva in southwestern Switzerland.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaef758b08190b9aa5ec7082cd417 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f73998221c8190a2d8982a3da28ec9 completed May 3, 2026, 12:03 p.m.
Created at: April 9, 2026, 9:41 p.m.