Triple

T4373585
Position Surface form Disambiguated ID Type / Status
Subject Milbanke family E98951 entity
Predicate hasSurnameForm P18 FINISHED
Object Milbanke E98951 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: Milbanke | Statement: [Milbanke family, hasSurnameForm, Milbanke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Milbanke
Context triple: [Milbanke family, hasSurnameForm, Milbanke]
  • A. Milbanke chosen
    Milbanke is an English aristocratic family name historically associated with the wife of poet Lord Byron, Annabella Milbanke.
  • B. Winifred
    Winifred is the given name of Winnie Madikizela-Mandela, the prominent South African anti-apartheid activist and politician.
  • C. Haggith
    Haggith is a lesser-known wife of King David in the Hebrew Bible and the mother of his son Adonijah.
  • D. Moira
    Moira is a feminine given name of Greek origin, often considered a variant of Mary and associated with meanings like "fate" or "destiny."
  • E. Maud
    Maud was a Norwegian polar exploration ship used by Roald Amundsen during his Arctic expeditions in the early 20th century.
  • 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_69b3454db3708190aeafd814413c4c3d completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35220fa648190b116e786783a7eba completed March 12, 2026, 11:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69b6135623888190bf7a4b558ca3e0d4 completed March 15, 2026, 2:03 a.m.
Created at: March 12, 2026, 11:17 p.m.