Triple

T22370724
Position Surface form Disambiguated ID Type / Status
Subject Von Koren E553031 entity
Predicate conflictsWith P4897 FINISHED
Object Laevsky 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: Laevsky | Statement: [Von Koren, conflictsWith, Laevsky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laevsky
Context triple: [Von Koren, conflictsWith, Laevsky]
  • A. Laevsky chosen
    Laevsky is the flawed, indecisive antihero of Anton Chekhov’s novella "The Duel," whose moral weakness and personal crisis drive the story’s central conflict.
  • B. Lomonosovo
    Lomonosovo is a rural locality in Russia’s Arkhangelsk Oblast, best known as the birthplace of the polymath Mikhail Lomonosov.
  • C. Nedomanský
    Nedomanský is a Czech surname most notably associated with Václav Nedomanský, a prominent former professional ice hockey player and Hall of Famer.
  • D. Kholmsk
    Kholmsk is a port town on the western coast of Sakhalin Island in Russia, serving as an important maritime transport hub in the Sea of Japan.
  • E. Orlovika
    Orlovika is an alternative name for the Orlov Revolt, an 18th-century Greek uprising against Ottoman rule encouraged by Russia during the Russo-Turkish War.
  • 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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15803e7208190ba14c91fb90e15ca completed April 29, 2026, 12:59 a.m.
Created at: April 16, 2026, 8:44 p.m.