Triple

T21975758
Position Surface form Disambiguated ID Type / Status
Subject J. E. H. MacDonald E542700 entity
Predicate familyName P18 FINISHED
Object MacDonald 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: MacDonald | Statement: [J. E. H. MacDonald, familyName, MacDonald]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MacDonald
Context triple: [J. E. H. MacDonald, familyName, MacDonald]
  • A. MacDonald chosen
    MacDonald is a common Scottish surname historically associated with the powerful Clan Donald and borne by numerous notable figures in politics, arts, and public life.
  • B. MacLamond
    MacLamond is a Scottish surname associated as a sept with Clan Lamont, a historic Highland clan from Argyll.
  • C. MacAndrew
    MacAndrew is a Scottish surname, historically a variant of Anderson, associated with families and clans of Gaelic origin.
  • D. Maclean
    Maclean is a riverside town in northern New South Wales, Australia, known for its strong Scottish heritage and annual Highland Gathering.
  • E. MacMurrie
    MacMurrie is a surname variant of Murray, a Scottish family name with Gaelic origins.
  • 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_69e0c48070988190909db97667b9a0ac completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f124886418819091daed0988432350 completed April 28, 2026, 9:20 p.m.
Created at: April 16, 2026, 8:03 p.m.