Triple

T5815876
Position Surface form Disambiguated ID Type / Status
Subject Andrei Krasnov E128983 entity
Predicate familyName P18 FINISHED
Object Krasnov E128983 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: Krasnov | Statement: [Andrei Krasnov, familyName, Krasnov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krasnov
Context triple: [Andrei Krasnov, familyName, Krasnov]
  • A. Krasnov chosen
    Krasnov is a Russian surname borne by various notable figures in military, political, and cultural history.
  • B. Kurskaya
    Kurskaya is a Moscow Metro station on the Koltsevaya (Circle) Line, serving as a major transfer hub in the city’s rapid transit network.
  • C. Chernyakhovsky
    Chernyakhovsky is a Slavic surname most notably associated with Soviet General Ivan Chernyakhovsky, a prominent commander during World War II.
  • D. Peshkov
    Peshkov is a Russian surname most famously borne by Alexei Maximovich Peshkov, better known by his pen name Maxim Gorky, a prominent writer and political activist.
  • E. Kamenskiy
    Kamenskiy is a Slavic surname, commonly transliterated from Russian or related languages, borne by various individuals across Eastern Europe and the former Soviet Union.
  • 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_69c0084869e881908d7859492183ca7b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0336344148190bcf417c0b9617cb9 completed March 22, 2026, 6:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0bfb903788190bae497fe72bd1e78 completed March 23, 2026, 4:21 a.m.
Created at: March 22, 2026, 3:53 p.m.