Triple

T3137520
Position Surface form Disambiguated ID Type / Status
Subject De Dam E65568 entity
Predicate hasAdjacentStreet P8235 FINISHED
Object Damstraat E66615 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: Damstraat | Statement: [De Dam, hasAdjacentStreet, Damstraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Damstraat
Context triple: [De Dam, hasAdjacentStreet, Damstraat]
  • A. Damstraat chosen
    Damstraat is a central street in Amsterdam’s historic city center, linking Dam Square with the Red Light District and lined with shops, cafés, and tourist-oriented businesses.
  • B. Domstraat
    Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
  • C. Westerstraat
    Westerstraat is a well-known street in Amsterdam’s historic Jordaan district, noted for its traditional architecture, local shops, and lively neighborhood atmosphere.
  • D. Spuistraat
    Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
  • E. Vijzelstraat
    Vijzelstraat is a major street in central Amsterdam, Netherlands, running between the city’s historic canals and serving as an important traffic and commercial route.
  • 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_69ad8581c25c8190b0d85ba9b9baa531 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada574509c81908a88bb10ea35516d completed March 8, 2026, 4:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69b324e2f1448190be5b744abdeed314 completed March 12, 2026, 8:41 p.m.
Created at: March 8, 2026, 3:05 p.m.