Triple

T23383380
Position Surface form Disambiguated ID Type / Status
Subject Hever railway station E593810 entity
Predicate locatedIn P40 FINISHED
Object Hever 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: Hever | Statement: [Hever railway station, locatedIn, Hever]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hever
Context triple: [Hever railway station, locatedIn, Hever]
  • A. Hever chosen
    Hever is a village in Kent, England, best known as the location of the historic Hever Castle, former childhood home of Anne Boleyn.
  • B. Hohberg
    Hohberg is a municipality in the Ortenau district of Baden-Württemberg in southwestern Germany.
  • C. Holtenau
    Holtenau is a district of the city of Kiel in northern Germany, situated at the entrance of the Kiel Canal and known for its maritime and aviation facilities.
  • D. Brackenheim
    Brackenheim is a small town in the German state of Baden-Württemberg, best known as the birthplace of Theodor Heuss, the first President of the Federal Republic of Germany.
  • E. Hasselager
    Hasselager is a residential neighborhood in the southern part of Aarhus, Denmark.
  • 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_69e25d268a50819095f2fd479da8ef3f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a496ae34819090e86c89eef6d2dc completed April 29, 2026, 6:26 a.m.
Created at: April 17, 2026, 5:34 p.m.