Triple

T3456314
Position Surface form Disambiguated ID Type / Status
Subject Dam Square E72911 entity
Predicate connectsWith P37 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: [Dam Square, connectsWith, Damstraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Damstraat
Context triple: [Dam Square, connectsWith, 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. Raadhuisstraat
    Raadhuisstraat is a central street in Amsterdam, Netherlands, known for connecting Dam Square to the Jordaan district and for its historic architecture and shops.
  • E. Spuistraat
    Spuistraat is a central street in Amsterdam known for its historic buildings, shops, and proximity to major city landmarks.
  • 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_69ad85b12a908190a1d10a6b03b4f8ae completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbaa77b9c81909376a5995cdaf6ac completed March 8, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3bb767b34819099b6f1cc4cae20a9 completed March 13, 2026, 7:23 a.m.
Created at: March 8, 2026, 3:16 p.m.