Triple

T19713495
Position Surface form Disambiguated ID Type / Status
Subject Bishop of Breda E473414 entity
Predicate locatedIn P40 FINISHED
Object Breda 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: Breda | Statement: [Bishop of Breda, locatedIn, Breda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Breda
Context triple: [Bishop of Breda, locatedIn, Breda]
  • A. Breda
    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. Breda, Netherlands chosen
    Breda, Netherlands is a historic city in the southern Dutch province of North Brabant, known for its medieval architecture, former status as a military stronghold, and vibrant cultural life.
  • D. Berghem
    Berghem is a village in the Dutch province of North Brabant that is now administratively part of the municipality of Oss.
  • E. Heverlee
    Heverlee is a suburb of Leuven in the Flemish Brabant province of Belgium, known for its residential areas, green spaces, and nearby university facilities.
  • 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_69d8e516dd048190a0b6c93ea3e71f58 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6440a0f2c8190803ace7f6b4ed6e9 completed April 20, 2026, 3:19 p.m.
Created at: April 10, 2026, 1:46 p.m.