Triple

T5993859
Position Surface form Disambiguated ID Type / Status
Subject Halderberge E133417 entity
Predicate locatedNear P294 FINISHED
Object Breda E151867 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: Breda | Statement: [Halderberge, locatedNear, Breda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Breda
Context triple: [Halderberge, locatedNear, Breda]
  • A. Breda chosen
    Breda is a historic city in the southern Netherlands known for its medieval architecture, former status as a military and political center, and vibrant cultural life.
  • B. Breda
    Breda is an Italian industrial company best known for manufacturing railway rolling stock, including trains and trams used in transit systems worldwide.
  • C. Berghem
    Berghem is a village in the Dutch province of North Brabant that is now administratively part of the municipality of Oss.
  • D. La Hulpe
    La Hulpe is a small, affluent municipality in Walloon Brabant, Belgium, known for its green surroundings and the Château de La Hulpe within the Solvay Regional Estate.
  • E. Rolandswerth
    Rolandswerth is a district of the German town of Remagen, situated along the Rhine River in the state of Rhineland-Palatinate.
  • 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_69c00870ddbc81909880fa3864f4f38d completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04e92e1448190bbf961a8243082ee completed March 22, 2026, 8:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c108685f788190aa3f84e56837b195 completed March 23, 2026, 9:31 a.m.
Created at: March 22, 2026, 4:05 p.m.