Triple

T15233663
Position Surface form Disambiguated ID Type / Status
Subject Jodenbreestraat E364067 entity
Predicate near P350 FINISHED
Object Nieuwmarkt E256497 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: Nieuwmarkt | Statement: [Jodenbreestraat, near, Nieuwmarkt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nieuwmarkt
Context triple: [Jodenbreestraat, near, Nieuwmarkt]
  • A. Nieuwmarkt chosen
    Nieuwmarkt is a historic square and lively neighborhood in central Amsterdam known for its markets, cafés, and the medieval Waag building.
  • B. Noordermarkt
    Noordermarkt is a historic square and popular market in Amsterdam’s Jordaan district, known for its organic farmers’ market and antique stalls.
  • C. Markt
    Markt is the central market square of Bruges, Belgium, known for its historic guild houses, bustling cafes, and prominent Belfry tower.
  • D. Oldemarkt
    Oldemarkt is a village in the Dutch province of Overijssel, known for its traditional character and location within the municipality of Steenwijkerland.
  • E. Marktl
    Marktl is a small Bavarian municipality best known as the birthplace of Pope Benedict XVI.
  • 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_69d85a0ce24c81909c4d3b6475548c95 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e007d7237081908dc17900ee66b64f completed April 15, 2026, 9:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fedd3dd5a081909a1a7fceda648c29 completed May 9, 2026, 7:07 a.m.
Created at: April 10, 2026, 3:12 a.m.