Triple

T21616007
Position Surface form Disambiguated ID Type / Status
Subject Lahntal railway E533438 entity
Predicate connects P390 FINISHED
Object Weilburg 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: Weilburg | Statement: [Lahntal railway, connects, Weilburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Weilburg
Context triple: [Lahntal railway, connects, Weilburg]
  • A. Weilburg chosen
    Weilburg is a historic town in the German state of Hesse, known for its Renaissance castle and as the ancestral seat of the House of Nassau-Weilburg.
  • B. Limburg-Weilburg
    Limburg-Weilburg is a rural district in the German state of Hesse, known for its historic town of Limburg an der Lahn and its location along the Lahn River.
  • C. Wiescheid
    Wiescheid is a district of the town of Langenfeld in North Rhine-Westphalia, Germany, characterized by its residential areas and proximity to surrounding green spaces.
  • D. Morbach
    Morbach is a small town in the Hunsrück region of Rhineland-Palatinate in western Germany, known for its scenic forests and rural landscapes.
  • E. Willebadessen
    Willebadessen is a small town in western Germany, located in the state of North Rhine-Westphalia.
  • 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_69e0c46411108190bba0d4176dffc9f3 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef3baab9e88190bc02f27133ef32d6 completed April 27, 2026, 10:34 a.m.
Created at: April 16, 2026, 6:33 p.m.