Triple

T3587419
Position Surface form Disambiguated ID Type / Status
Subject Binnenstad E75944 entity
Predicate contains P35 FINISHED
Object Domplein E276260 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: Domplein | Statement: [Binnenstad, contains, Domplein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Domplein
Context triple: [Binnenstad, contains, Domplein]
  • A. Domplein Utrecht chosen
    Domplein in Utrecht is the historic central square of the city, known for its Roman and medieval archaeological remains and as the site of the iconic Dom Tower and cathedral complex.
  • B. Leidseplein
    Leidseplein is a lively square in central Amsterdam known for its theaters, nightlife, street performers, and numerous cafés and restaurants.
  • C. Molengracht Plaza
    Molengracht Plaza is a Dutch-inspired town square and commercial district in Pella, Iowa, featuring canals, shops, and community gathering spaces.
  • D. Muntplein
    Muntplein is a central square in Amsterdam, known as a busy traffic hub near the historic city center and the Munttoren (Mint Tower).
  • E. Weesperplein
    Weesperplein is an underground metro station in central Amsterdam that serves as a key stop on multiple Amsterdam Metro lines.
  • 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_69ad85d6dc3c8190b491b79b83e25461 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc13a11608190a23d76efc1b50e3c completed March 8, 2026, 6:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4030088548190adbb029be1caeb81 completed March 13, 2026, 12:28 p.m.
Created at: March 8, 2026, 3:22 p.m.