Triple

T6443604
Position Surface form Disambiguated ID Type / Status
Subject Alliluev E138284 entity
Predicate hasFeminineForm P1613 FINISHED
Object Allilueva E595013 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: Allilueva | Statement: [Alliluev, hasFeminineForm, Allilueva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Allilueva
Context triple: [Alliluev, hasFeminineForm, Allilueva]
  • A. Allilueva chosen
    Allilueva is a Russian feminine surname, most notably borne by Nadezhda Alliluyeva, the second wife of Soviet leader Joseph Stalin.
  • B. Khimki
    Khimki is a city in Moscow Oblast, Russia, forming part of the Moscow metropolitan area and known for its proximity to major transport hubs and industrial facilities.
  • C. Lübars
    Lübars is a historic, village-like district in Berlin’s Reinickendorf borough, known for its rural character, fields, and preserved traditional architecture within the city.
  • D. Luzhitsy
    Luzhitsy is a rural village in northwestern Russia historically associated with the Votic people and their traditional language and culture.
  • E. Karlino
    Karlino is a small town in northwestern Poland known for its location in the historical region of Pomerania.
  • 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_69c008aa61ac8190bc96715ed79fe2d8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0698b030481908b7bb4e16a8b3339 completed March 22, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69c65390257c819097706c35b3aebc8e completed March 27, 2026, 9:53 a.m.
Created at: March 22, 2026, 4:46 p.m.