Triple

T4030715
Position Surface form Disambiguated ID Type / Status
Subject Anglo-Saxon England E83701 entity
Predicate hasPart P35 FINISHED
Object Danelaw E384778 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: Danelaw | Statement: [Anglo-Saxon England, hasPart, Danelaw]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Danelaw
Context triple: [Anglo-Saxon England, hasPart, Danelaw]
  • A. Danelaw chosen
    Danelaw was a historical region of England under Scandinavian control and influence, characterized by Norse law, culture, and settlement during the early Middle Ages.
  • B. Dannevirke
    Dannevirke is a rural service town in New Zealand known for its Scandinavian heritage and farming-based economy.
  • C. Vinland
    Vinland is the name given in Norse sagas to a region of coastal North America explored by Viking seafarers around the 10th–11th centuries, often identified with areas of Atlantic Canada.
  • D. Geatland
    Geatland is the homeland of the hero Beowulf, depicted in the Old English epic as the territory of the Geats in what is now southern Sweden.
  • E. Svealand
    Svealand is the central region of Sweden, historically significant as the country's core area and home to the capital city, Stockholm.
  • 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_69aed92e29ac819080f7a98b594fec05 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb0dbb8481909ff2ee49dadcd1dc completed March 9, 2026, 4:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5629748d88190984cce08eef05e9c completed March 14, 2026, 1:28 p.m.
Created at: March 9, 2026, 3:36 p.m.