Triple

T16578859
Position Surface form Disambiguated ID Type / Status
Subject Lindum Colonia E402785 entity
Predicate hasFormerName P65 FINISHED
Object Lindum E91562 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: Lindum | Statement: [Lindum Colonia, hasFormerName, Lindum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lindum
Context triple: [Lindum Colonia, hasFormerName, Lindum]
  • A. Haderup
    Haderup is a small town in Denmark, known locally as a rural community that gave its name to the former Aulum-Haderup Municipality.
  • B. Lindum Colonia chosen
    Lindum Colonia was the Roman settlement and colonia that developed into the modern city of Lincoln in Lincolnshire, England.
  • C. Padborg
    Padborg is a Danish town in Southern Jutland known as an important transport and border crossing hub between Denmark and Germany.
  • D. Hellebæk
    Hellebæk is a coastal town in northeastern Zealand, Denmark, known for its scenic setting near Helsingør and its historic industrial and residential architecture.
  • E. Knudshoved
    Knudshoved is a coastal area on the Danish island of Funen that serves as a key transport hub and former ferry terminal at the western end of the Great Belt crossing.
  • 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3595f9be88190b01ba628ecf1103d completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a006eee7e4881908a529717bc449078 completed May 10, 2026, 11:41 a.m.
Created at: April 10, 2026, 5:16 a.m.