Triple

T184352
Position Surface form Disambiguated ID Type / Status
Subject Singel E3947 entity
Predicate adjacentTo P224 FINISHED
Object Koningsplein E28240 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: [Singel, adjacentTo, Koningsplein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Koningsplein
Context triple: [Singel, adjacentTo, Koningsplein]
  • A. Utrechtsestraat
    Utrechtsestraat is a well-known shopping and dining street in central Amsterdam, noted for its historic canalside setting and mix of boutiques, cafés, and restaurants.
  • B. Muntplein chosen
    Muntplein is a central square in Amsterdam, known as a busy traffic hub near the historic city center and the Munttoren (Mint Tower).
  • C. Vijzelstraat
    Vijzelstraat is a major street in central Amsterdam, Netherlands, running between the city’s historic canals and serving as an important traffic and commercial route.
  • D. Prinsengracht
    Prinsengracht is one of Amsterdam’s main historic canals, known for its picturesque waterways, houseboats, and traditional canal houses.
  • E. Keizersgracht
    Keizersgracht is one of Amsterdam’s main historic canals, renowned for its grand 17th-century canal houses and central role in the city’s UNESCO-listed canal belt.
  • 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_69a25497e2f08190a040f8c6e1842643 completed Feb. 28, 2026, 2:36 a.m.
NER Named-entity recognition batch_69a25926be9c8190a4cfce66f57589d1 completed Feb. 28, 2026, 2:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3672cae0c819086233f16cc2003de completed Feb. 28, 2026, 10:07 p.m.
Created at: Feb. 28, 2026, 2:40 a.m.