Triple

T18236902
Position Surface form Disambiguated ID Type / Status
Subject Moskovici E436704 entity
Predicate isRelatedSurname P3889 FINISHED
Object Moscovici 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: Moscovici | Statement: [Moskovici, isRelatedSurname, Moscovici]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moscovici
Context triple: [Moskovici, isRelatedSurname, Moscovici]
  • A. Malinovsky
    Malinovsky is a Russian surname most notably associated with Soviet military commander and Marshal of the Soviet Union Rodion Malinovsky.
  • B. Moscavide
    Moscavide is an urban parish in the municipality of Loures, within the Lisbon metropolitan area of Portugal.
  • C. Moskvin
    Moskvin is a Russian surname borne by various notable individuals in fields such as the arts, sports, and academia.
  • D. Khoyski
    Khoyski is the surname of an Azerbaijani noble and political family best known for Fatali Khan Khoyski, the first Prime Minister of the Azerbaijan Democratic Republic.
  • E. Moskovici chosen
    Moskovici is a variant spelling of the surname Moskovitz, which is of Eastern European Jewish origin.
  • 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_69d8b91104e08190a8241f7d260a5162 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4f7def3c48190a9a96c8b4911f0f3 completed April 19, 2026, 3:42 p.m.
Created at: April 10, 2026, 10:33 a.m.