Triple

T14020064
Position Surface form Disambiguated ID Type / Status
Subject Dappermarkt E337306 entity
Predicate street P959 FINISHED
Object Dapperstraat E1081065 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: Dapperstraat | Statement: [Dappermarkt, street, Dapperstraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dapperstraat
Context triple: [Dappermarkt, street, Dapperstraat]
  • A. Dapperstraat chosen
    Dapperstraat is a well-known shopping and market street in Amsterdam, noted for the daily Dappermarkt and its lively, multicultural atmosphere.
  • B. Schupstraat
    Schupstraat is a prominent street in Antwerp’s Diamond District, known for its dense concentration of diamond shops and related businesses.
  • C. Breidelstraat
    Breidelstraat is a historic street in the center of Bruges, Belgium, connecting the Markt square with other medieval lanes and lined with traditional Flemish architecture.
  • D. Hartenstraat
    Hartenstraat is one of the small, picturesque shopping streets in Amsterdam’s historic Negen Straatjes (Nine Streets) district, known for its boutiques, cafés, and canal-side charm.
  • E. Domstraat
    Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
  • 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_69d81c6543a48190bd5ba93d7419e797 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2f3c7cd88190b236382058581740 completed April 14, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd192ee1ac81908663ebd2e06784f1 completed May 7, 2026, 10:58 p.m.
Created at: April 9, 2026, 10:19 p.m.