Triple

T23418225
Position Surface form Disambiguated ID Type / Status
Subject Gundestrup cauldron E560571 entity
Predicate discoveredIn P3986 FINISHED
Object Himmerland NE NERFINISHED

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: Himmerland | Statement: [Gundestrup cauldron, discoveredIn, Himmerland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Himmerland
Context triple: [Gundestrup cauldron, discoveredIn, Himmerland]
  • A. Himmerland chosen
    Himmerland is a large peninsula in northern Jutland, Denmark, known for its rural landscapes, coastal areas, and small towns.
  • B. Hemmeland
    Hemmeland is a small settlement in the Dutch municipality of Waterland, located in the province of North Holland in the Netherlands.
  • C. Skaland
    Skaland is a small coastal village on the island of Senja in northern Norway, known for its scenic fjord landscape and proximity to rugged mountains.
  • D. Kvernaland
    Kvernaland is a village in Rogaland county, Norway, known for its agricultural machinery industry and proximity to the city of Stavanger.
  • E. Søndre Lænding
    Søndre Lænding is the term for a resident or native of the Norwegian municipality of Søndre Land.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e2454cb1108190ab21ada5411a7146 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1a5438ac08190a40a3d6402794699 completed April 29, 2026, 6:29 a.m.
Created at: April 17, 2026, 5:39 p.m.