Triple

T18957186
Position Surface form Disambiguated ID Type / Status
Subject Arkadiy Abramovich E463810 entity
Predicate familyName P18 FINISHED
Object Abramovich 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: Abramovich | Statement: [Arkadiy Abramovich, familyName, Abramovich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abramovich
Context triple: [Arkadiy Abramovich, familyName, Abramovich]
  • A. Abramovich chosen
    Abramovich is a Russian patronymic derived from the male given name Abram, indicating "son of Abram."
  • B. Aaron Abramovich
    Aaron Abramovich is one of the children of Russian-Israeli billionaire and former Chelsea F.C. owner Roman Abramovich.
  • C. Roman Abramovich
    Roman Abramovich is a Russian-Israeli billionaire businessman and investor best known for his long tenure as owner of the English football club Chelsea FC and his prominent role among Russia’s post-Soviet oligarchs.
  • D. Arkadiy Abramovich
    Arkadiy Abramovich is a Russian businessman and investor, known as the son of billionaire and former Chelsea F.C. owner Roman Abramovich.
  • E. Rybolovlev
    Rybolovlev is a Russian surname most prominently associated with billionaire businessman and art collector Dmitry Rybolovlev.
  • 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d5cee8348190b6506b10aed6c58a completed April 20, 2026, 7:29 a.m.
Created at: April 10, 2026, noon