Triple

T12529616
Position Surface form Disambiguated ID Type / Status
Subject Clan MacInnes E299525 entity
Predicate hasSurnameForm P18 FINISHED
Object McInnes E986231 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: McInnes | Statement: [Clan MacInnes, hasSurnameForm, McInnes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: McInnes
Context triple: [Clan MacInnes, hasSurnameForm, McInnes]
  • A. MacInnis
    MacInnis is a Scottish surname associated with Clan MacInnes, a Highland clan with historical roots in the western coastal regions of Scotland.
  • B. McInness chosen
    McInness is a Scottish surname associated with Clan MacInnes, a Highland clan of ancient origin.
  • C. MacInness
    MacInness is a Scottish surname associated as a sept with Clan MacInnes of the Scottish Highlands.
  • D. McAvennie
    McAvennie is the surname of Frank McAvennie, a former Scottish professional footballer best known for his prolific goal-scoring spells with St Mirren, West Ham United, and Celtic in the 1980s.
  • E. Strachan
    Strachan is a Scottish surname of Gaelic origin associated with various notable individuals and a historic clan from the Aberdeenshire region of Scotland.
  • 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_69d6ada5cdd48190860d9ce30aff69be completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95469d100819087c83bc55e3ec9ce completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f655762ae88190ab41e23bbd65c566 completed May 2, 2026, 7:50 p.m.
Created at: April 8, 2026, 9:57 p.m.