Triple

T5591686
Position Surface form Disambiguated ID Type / Status
Subject Panorama Route E146892 entity
Predicate startsNear P8203 FINISHED
Object Lydenburg E150617 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: Lydenburg | Statement: [Panorama Route, startsNear, Lydenburg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lydenburg
Context triple: [Panorama Route, startsNear, Lydenburg]
  • A. Lydenburg chosen
    Lydenburg is a historic town in South Africa known for its early gold-mining heritage and proximity to scenic routes and nature reserves in the Mpumalanga province.
  • B. Lutzenberg
    Lutzenberg is a small municipality in the canton of Appenzell Ausserrhoden in northeastern Switzerland.
  • C. Löwenberg
    Löwenberg is a town in Germany known for its cultural and municipal partnership as a twin town of Weilburg.
  • D. Bromberg
    Bromberg is the former German name for the city of Bydgoszcz, a major urban and industrial center in present-day north-central Poland.
  • E. Neubukow
    Neubukow is a small town in northern Germany best known as the birthplace of archaeologist Heinrich Schliemann.
  • 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_69c009036c408190981a8d690b679b67 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020a3365c8190bd223226c0a6969f completed March 22, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c04d38161881909af592db1180e55f completed March 22, 2026, 8:12 p.m.
Created at: March 22, 2026, 3:38 p.m.