Triple

T21127672
Position Surface form Disambiguated ID Type / Status
Subject Great Danish Army E520599 entity
Predicate leader P981 FINISHED
Object Anund E520606 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: Anund | Statement: [Great Danish Army, leader, Anund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anund
Context triple: [Great Danish Army, leader, Anund]
  • A. Anund chosen
    Anund was a Viking chieftain who served as one of the leaders of the Great Heathen Army during its campaigns in England in the late 9th century.
  • B. Anund Jacob
    Anund Jacob was an early 11th-century king of Sweden known for his Christian rule and efforts to strengthen royal power and ties with neighboring kingdoms.
  • C. Ulf Jarl
    Ulf Jarl was an influential early 11th-century Danish nobleman and military leader, brother-in-law to King Cnut the Great and father of the later Danish king Sweyn II.
  • D. Orpund
    Orpund is a municipality in the canton of Bern in Switzerland, situated near the city of Biel/Bienne.
  • E. Ulf
    Ulf is a masculine given name of Germanic origin, commonly used in German and Scandinavian countries.
  • 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_69e0b50a623881909c0bbaf4f2c055e7 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7223a7a588190a01a66921b79b98b completed April 21, 2026, 7:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0965ee05c0819084273a47c09d7d2f completed May 17, 2026, 6:53 a.m.
Created at: April 16, 2026, 2:56 p.m.