Triple

T11224929
Position Surface form Disambiguated ID Type / Status
Subject Havelian Dry Port E265669 entity
Predicate locatedIn P40 FINISHED
Object Havelian E271514 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: Havelian | Statement: [Havelian Dry Port, locatedIn, Havelian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Havelian
Context triple: [Havelian Dry Port, locatedIn, Havelian]
  • A. Havelian chosen
    Havelian is a town in Pakistan’s Khyber Pakhtunkhwa province, known as a local commercial center and a key junction on the Karakoram Highway.
  • B. Haveltermade
    Haveltermade is a residential district of the Dutch city of Meppel in the province of Drenthe.
  • C. Havel
    The Havel is a river in northeastern Germany that flows through Berlin and Brandenburg before joining the Elbe.
  • D. Havlíček
    Havlíček is a Czech surname most famously associated with basketball Hall of Famer John Havlicek and several notable Czech cultural and public figures.
  • E. Moholy
    Moholy is a surname most notably associated with figures linked to the Bauhaus movement, such as photographer and writer Lucia Moholy.
  • 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_69d6aac656d48190b275efaa7d6074ee completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8ee15d4819087449058addef597 completed April 9, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4ad269b248190bb72e560e3efc0ce completed April 19, 2026, 10:23 a.m.
Created at: April 8, 2026, 9:30 p.m.