Triple

T9723701
Position Surface form Disambiguated ID Type / Status
Subject Zweibrücken E235546 entity
Predicate near P350 FINISHED
Object Saarbrücken E269297 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: Saarbrücken | Statement: [Zweibrücken, near, Saarbrücken]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saarbrücken
Context triple: [Zweibrücken, near, Saarbrücken]
  • A. Saarbrücken chosen
    Saarbrücken is a German city on the Saar River known as an industrial, cultural, and educational center near the French border.
  • B. Saarlouis
    Saarlouis is a town in the German state of Saarland, known historically as a fortified city founded by Louis XIV of France near the French border.
  • C. Wissembourg
    Wissembourg is a historic town in northeastern France’s Alsace region, known for its well-preserved medieval architecture and proximity to the German border.
  • D. Kaiserslautern
    Kaiserslautern is a city in southwestern Germany known for its historic old town, technical university, and prominent football club 1. FC Kaiserslautern.
  • E. Lörrach
    Lörrach is a town in southwest Germany’s Baden-Württemberg state, near the borders with Switzerland and France, known for its proximity to Basel and its role as a regional economic and cultural center.
  • 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_69ca84d0123c819096f9dc3b6abb0881 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9e77096481908ffd315fecb1d5ec completed April 1, 2026, 10:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69d25753fec48190927e8d96efd2df54 completed April 5, 2026, 12:36 p.m.
Created at: March 30, 2026, 8:20 p.m.