Triple

T18864367
Position Surface form Disambiguated ID Type / Status
Subject Hamtun E461397 entity
Predicate instanceOf P0 FINISHED
Object early medieval English place-name C16156 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: early medieval English place-name
Context triple: [Hamtun, instanceOf, early medieval English place-name]
  • A. medieval English name
    A medieval English name is a personal name used in England roughly between the 5th and 15th centuries, often reflecting Old English, Norman, or Latin influences and frequently tied to religious, occupational, or locational origins.
  • B. Old English toponym chosen
    An Old English toponym is a place-name whose form and meaning originate from the Old English language, often reflecting early medieval landscape features, settlements, or ownership.
  • C. early medieval site
    An early medieval site is an archaeological location dating roughly from the 5th to the 11th century CE that preserves material evidence of social, political, economic, and religious life during the early Middle Ages.
  • D. early medieval period
    The early medieval period is a historical era roughly spanning the 5th to the 10th centuries CE, marked by the transformation of the Roman world, the formation of new kingdoms, the spread of Christianity and Islam, and the gradual development of medieval European, Byzantine, and Islamic civilizations.
  • E. historical place name
    A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
  • F. None of above.

Provenance (1 batch)

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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
Created at: April 10, 2026, 11:57 a.m.