Triple

T1614753
Position Surface form Disambiguated ID Type / Status
Subject Blauwbrug E34690 entity
Predicate connects P390 FINISHED
Object Waterlooplein E194082 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: Waterlooplein | Statement: [Blauwbrug, connects, Waterlooplein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Waterlooplein
Context triple: [Blauwbrug, connects, Waterlooplein]
  • A. Waterlooplein square chosen
    Waterlooplein square is a central square in Amsterdam best known for its historic daily flea market and proximity to major cultural and civic buildings.
  • B. Leidseplein
    Leidseplein is a lively square in central Amsterdam known for its theaters, nightlife, street performers, and numerous cafés and restaurants.
  • C. Luxemburgplein
    Luxemburgplein is a prominent square in Brussels, Belgium, located near the European Parliament and known as a hub for political and social gatherings.
  • D. Koningsplein
    Koningsplein is a central square in Amsterdam known for its proximity to major canals, shopping streets, and the historic city center.
  • E. Paleizenplein
    Paleizenplein is the prominent public square in central Brussels that fronts the Royal Palace and serves as a key ceremonial and urban landmark in the Belgian capital.
  • 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9098f384c81909ef836ee779466e2 completed March 5, 2026, 4:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69adeac40c608190800da8b029ef065a completed March 8, 2026, 9:31 p.m.
Created at: March 4, 2026, 7:28 p.m.