Triple

T17209380
Position Surface form Disambiguated ID Type / Status
Subject Koningsplein E417683 entity
Predicate hasNameInDutch P13254 FINISHED
Object Koningsplein E129993 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: Koningsplein | Statement: [Koningsplein, hasNameInDutch, Koningsplein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koningsplein
Context triple: [Koningsplein, hasNameInDutch, Koningsplein]
  • A. Koningsplein chosen
    Koningsplein is a central square in Amsterdam known for its proximity to major canals, shopping streets, and the historic city center.
  • B. Koningsplein
    Koningsplein is a prominent neoclassical square in central Brussels known for its historic buildings and cultural significance.
  • 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. Merwedeplein
    Merwedeplein is a residential square in Amsterdam best known for being the neighborhood where Anne Frank lived before going into hiding.
  • 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_69d886d779488190b131369541c04e7d completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42dc3b0ec8190b8c9fc401da5770c completed April 19, 2026, 1:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a015fe0a28c8190a76b3a356f7e0478 completed May 11, 2026, 4:49 a.m.
Created at: April 10, 2026, 5:38 a.m.