Triple

T11021629
Position Surface form Disambiguated ID Type / Status
Subject Aleksandra E260502 entity
Predicate hasVariant P455 FINISHED
Object Aleksandrina E140338 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: Aleksandrina | Statement: [Aleksandra, hasVariant, Aleksandrina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aleksandrina
Context triple: [Aleksandra, hasVariant, Aleksandrina]
  • A. Alexandrina chosen
    Alexandrina was the first given name of Queen Victoria, the long-reigning 19th-century British monarch.
  • B. Elisabeta
    Elisabeta is a given name used in various European languages, corresponding to the English name Elizabeth.
  • C. Alexandra
    Alexandra is a densely populated township in northern Johannesburg, South Africa, known for its vibrant culture and significant role in the country’s anti-apartheid history.
  • D. Alexandra
    Alexandra is a feminine given name of Greek origin meaning "defender of mankind," used in many cultures around the world.
  • E. Alexandra
    Alexandra is a small Central Otago town in New Zealand known for its riverside setting, fruit orchards, and historic gold-mining heritage.
  • 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_69d6aa9687448190b28d353b1b6a610e completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d797bb6eec81909d8004af31f307f7 completed April 9, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3a997d7bc8190982467039e0f5504 completed April 18, 2026, 3:56 p.m.
Created at: April 8, 2026, 9:25 p.m.