Triple

T23177017
Position Surface form Disambiguated ID Type / Status
Subject Æthelfrith of Northumbria E579031 entity
Predicate battle P12 FINISHED
Object Battle of Degsastan NE NERFINISHED

How this triple was built (3 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: Battle of Degsastan | Statement: [Æthelfrith of Northumbria, battle, Battle of Degsastan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Battle of Degsastan
Context triple: [Æthelfrith of Northumbria, battle, Battle of Degsastan]
  • A. Battle of Sitabuldi
    The Battle of Sitabuldi was a key 1817 engagement near Nagpur in central India, where British forces decisively defeated Maratha troops, helping to secure British dominance during the Third Anglo-Maratha War.
  • B. Battle of Baksar
    The Battle of Baksar was a decisive 1764 conflict in eastern India in which the British East India Company defeated a coalition of Indian rulers, paving the way for British dominance in Bengal and much of northern India.
  • C. Battle of Dibaltum
    The Battle of Dibaltum was a significant clash during the Gothic War (376–382) in which Gothic forces defeated the Eastern Roman army in the Balkans, contributing to the mounting crises of the late Roman Empire.
  • D. Battle of Mihmandoost
    The Battle of Mihmandoost was an early 18th-century engagement in Iran that formed part of Nader Shah’s rise to power during the campaigns that restored Safavid authority.
  • E. Battle of Kushk
    The Battle of Kushk, also known as the Panjdeh incident, was an 1885 border clash between the Russian Empire and Afghanistan that nearly triggered a war between Russia and the British Empire during the Great Game in Central Asia.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Battle of Degsastan
Target entity description: The Battle of Degsastan was a pivotal early 7th-century conflict in which the Northumbrian king Æthelfrith decisively defeated a coalition of Scots and Britons, helping to secure Northumbrian dominance in northern Britain.
  • A. Battle of Sitabuldi
    The Battle of Sitabuldi was a key 1817 engagement near Nagpur in central India, where British forces decisively defeated Maratha troops, helping to secure British dominance during the Third Anglo-Maratha War.
  • B. Battle of Baksar
    The Battle of Baksar was a decisive 1764 conflict in eastern India in which the British East India Company defeated a coalition of Indian rulers, paving the way for British dominance in Bengal and much of northern India.
  • C. Battle of Dibaltum
    The Battle of Dibaltum was a significant clash during the Gothic War (376–382) in which Gothic forces defeated the Eastern Roman army in the Balkans, contributing to the mounting crises of the late Roman Empire.
  • D. Battle of Mihmandoost
    The Battle of Mihmandoost was an early 18th-century engagement in Iran that formed part of Nader Shah’s rise to power during the campaigns that restored Safavid authority.
  • E. Battle of Kushk
    The Battle of Kushk, also known as the Panjdeh incident, was an 1885 border clash between the Russian Empire and Afghanistan that nearly triggered a war between Russia and the British Empire during the Great Game in Central Asia.
  • F. None of above. chosen

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_69e245fd2a388190b814c0dfa15f7148 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f6b823c8190a2d39c54e48a1001 completed April 29, 2026, 4:56 a.m.
Created at: April 17, 2026, 4:04 p.m.