Triple

T4162481
Position Surface form Disambiguated ID Type / Status
Subject Lindum Colonia E91562 entity
Predicate hasAlternativeName P39 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, hasAlternativeName, Lindum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lindum
Context triple: [Lindum Colonia, hasAlternativeName, Lindum]
  • A. Lindum Colonia chosen
    Lindum Colonia was the Roman settlement and colonia that developed into the modern city of Lincoln in Lincolnshire, England.
  • B. 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.
  • C. Ringsted
    Ringsted is a historic market town and transport hub located in the central part of the Danish island of Zealand.
  • D. Gudhjem
    Gudhjem is a picturesque coastal village on the Danish island of Bornholm, known for its steep streets, red-roofed houses, and harbor overlooking the Baltic Sea.
  • E. Haderslev
    Haderslev is a historic town in southern Denmark known for its medieval cathedral, old town center, and role as a regional cultural and administrative hub.
  • 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_69aed9626ebc8190a39de631788bea3e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af02a811608190aff8b663498711e8 completed March 9, 2026, 5:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f456bf88190b9b8678476ac3803 completed March 14, 2026, 3:31 p.m.
Created at: March 9, 2026, 3:44 p.m.