Triple

T14772959
Position Surface form Disambiguated ID Type / Status
Subject Lavr Kornilov E347181 entity
Predicate givenName P17 FINISHED
Object Lavr E347181 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: Lavr | Statement: [Lavr Kornilov, givenName, Lavr]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lavr
Context triple: [Lavr Kornilov, givenName, Lavr]
  • A. Lavr chosen
    Lavr is the given name of Lavr Kornilov, a prominent Russian military officer and key figure in the events surrounding the Russian Revolution.
  • B. Lyova
    Lyova is a Russian diminutive form of the male given name Lev.
  • C. Lavrans
    Lavrans is a central character in Sigrid Undset’s medieval Norwegian novel "Kristin Lavransdatter," known primarily as the devoted and principled father of the protagonist, Kristin.
  • D. Larionov
    Larionov is a person after whom the KLM line is named, likely recognized for notable contributions or significance related to that context.
  • E. Vaslav
    Vaslav is the given name of Vaslav Nijinsky, the legendary early 20th-century ballet dancer and choreographer renowned for his groundbreaking work with the Ballets Russes.
  • 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_69d822e9b9e08190bedcc31a163fda82 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec81485e08190be35baafcf22b6f2 completed April 14, 2026, 11:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe0cfd26fc81909fba39c8705437ed completed May 8, 2026, 4:19 p.m.
Created at: April 10, 2026, 1:31 a.m.