Triple

T2046659
Position Surface form Disambiguated ID Type / Status
Subject Battle of Tweebosch E45467 entity
Predicate commander P1061 FINISHED
Object Lord Methuen E226858 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: Lord Methuen | Statement: [Battle of Tweebosch, commander, Lord Methuen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lord Methuen
Context triple: [Battle of Tweebosch, commander, Lord Methuen]
  • A. Lord Methuen chosen
    Lord Methuen was a British Army general best known for his leadership during the Second Boer War, particularly in the early, often controversial, engagements.
  • B. Lord Haddo
    Lord Haddo is a courtesy title traditionally borne by the heir apparent to the Earl of Aberdeen in the Scottish peerage.
  • C. Lord Lyon
    Lord Lyon is the chief heraldic authority in Scotland, responsible for regulating coats of arms and overseeing matters of genealogy and state ceremonial.
  • D. Lord Lorne
    Lord Lorne is a courtesy title traditionally borne by the heir apparent to the Duke of Argyll in the Scottish peerage.
  • E. Lord Linlithgow
    Lord Linlithgow was a British statesman and colonial administrator best known for serving as Viceroy of India during the critical years leading up to and including much of the Second World War.
  • 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_69a8891948208190ab7898da21824c77 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb973a51881908c2c1e633daa3cb4 completed March 7, 2026, 5:36 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae2003e9488190b54ff042c91d4a62 completed March 9, 2026, 1:19 a.m.
Created at: March 4, 2026, 7:39 p.m.