Triple

T21691341
Position Surface form Disambiguated ID Type / Status
Subject Sedov E535375 entity
Predicate hasFeminineForm P1613 FINISHED
Object Sedova 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: Sedova | Statement: [Sedov, hasFeminineForm, Sedova]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sedova
Context triple: [Sedov, hasFeminineForm, Sedova]
  • A. Sedova chosen
    Sedova is a Russian surname most notably associated with revolutionary figure Natalia Sedova, the second wife of Leon Trotsky.
  • B. Sosva
    Sosva is a rural locality in Sverdlovsk Oblast, Russia, historically known as the site of a Soviet-era labor camp where Finnish communist leader Kullervo Manner died.
  • C. Tisová
    Tisová is a small settlement in the Karlovy Vary Region of the Czech Republic, known for its location near the Rolava River and the Ore Mountains.
  • D. Slaná
    Slaná is a river in central Europe that flows through Slovakia and Hungary, where it is known as the Sajó.
  • E. Moravice
    Moravice is a river in the northern part of the historical Moravia region of the Czech Republic.
  • 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_69e0c46a6ee481908836e1420fb78c9b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef96cfaab08190b400e1538afc8c43 completed April 27, 2026, 5:03 p.m.
Created at: April 16, 2026, 6:45 p.m.