Triple

T19173154
Position Surface form Disambiguated ID Type / Status
Subject Hippolyte Kuragin E469375 entity
Predicate familyName P18 FINISHED
Object Kuragin 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: Kuragin | Statement: [Hippolyte Kuragin, familyName, Kuragin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuragin
Context triple: [Hippolyte Kuragin, familyName, Kuragin]
  • A. Kuragin chosen
    Kuragin is the aristocratic Russian family name borne by several characters in Leo Tolstoy’s novel "War and Peace," including the rakish nobleman Anatole.
  • B. Nitobe
    Nitobe is a Japanese surname most notably associated with Inazo Nitobe, a prominent educator, diplomat, and author of "Bushido: The Soul of Japan."
  • C. Lopukhin
    Lopukhin is a Russian surname historically associated with a noble family of the Russian Empire.
  • D. Georgy Shonin
    Georgy Shonin was a Soviet cosmonaut and pilot who flew on the Soyuz 6 mission in 1969 and later became a prominent aviation and space program official.
  • E. Kenjirō
    Kenjirō is a Japanese masculine given name that can be written with various kanji combinations and is borne by multiple notable individuals in fields such as sports, arts, and entertainment.
  • 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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f16544948190bd10ca7804dd27a5 completed April 20, 2026, 9:27 a.m.
Created at: April 10, 2026, 12:06 p.m.