Triple

T11625636
Position Surface form Disambiguated ID Type / Status
Subject Domplein Utrecht E276260 entity
Predicate near P350 FINISHED
Object Domstraat E295549 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: Domstraat | Statement: [Domplein Utrecht, near, Domstraat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Domstraat
Context triple: [Domplein Utrecht, near, Domstraat]
  • A. Domstraat chosen
    Domstraat is a historic street in the center of Utrecht, Netherlands, connecting key landmarks around the Dom Tower and cathedral.
  • B. Schupstraat
    Schupstraat is a prominent street in Antwerp’s Diamond District, known for its dense concentration of diamond shops and related businesses.
  • C. Damstraat
    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.
  • 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. 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.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a12416908190ac2dcd7f7ebb308f completed April 10, 2026, 7:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69f019075f4c81908e0cde830231b229 completed April 28, 2026, 2:18 a.m.
Created at: April 8, 2026, 9:39 p.m.