Triple

T18004367
Position Surface form Disambiguated ID Type / Status
Subject Alexandrine E430706 entity
Predicate relatedName P3889 FINISHED
Object Alexandra 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: Alexandra | Statement: [Alexandrine, relatedName, Alexandra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Alexandra
Context triple: [Alexandrine, relatedName, Alexandra]
  • A. 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.
  • B. Alexandra chosen
    Alexandra is a feminine given name of Greek origin meaning "defender of mankind," used in many cultures around the world.
  • C. Alexandra
    Alexandra is a small Central Otago town in New Zealand known for its riverside setting, fruit orchards, and historic gold-mining heritage.
  • D. Viktoriya
    Viktoriya is a feminine given name, commonly used in Slavic countries as a variant of Victoria.
  • E. Alexis of Russia
    Alexis of Russia was the second Romanov tsar of Russia, ruling from 1645 to 1676 and overseeing significant territorial expansion and internal reforms that shaped the future Russian state.
  • 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b3eb1f748190904c8894d22cf85f completed April 19, 2026, 10:52 a.m.
Created at: April 10, 2026, 10:23 a.m.