Triple

T20243178
Position Surface form Disambiguated ID Type / Status
Subject Stadionkade E498350 entity
Predicate locatedNear P294 FINISHED
Object Stadionweg NE NERFINISHED

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: Stadionweg | Statement: [Stadionkade, locatedNear, Stadionweg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stadionweg
Context triple: [Stadionkade, locatedNear, Stadionweg]
  • A. Stadionweg chosen
    Stadionweg is a major street in Amsterdam’s Oud-Zuid district, known for its residential character and early 20th-century architecture.
  • B. Stadionplein
    Stadionplein is a public square and traffic hub in Amsterdam’s Zuid district, known for its proximity to the Olympic Stadium and its mix of residential, commercial, and event-related functions.
  • C. Sportlaan
    Sportlaan is a tram stop on the Amstelveenlijn light rail route serving the municipality of Amstelveen in the Amsterdam metropolitan area.
  • D. Willemsparkweg
    Willemsparkweg is a prominent street in Amsterdam’s Oud-Zuid district, known for its upscale residential buildings, boutiques, and proximity to the Vondelpark.
  • E. Scheveningseweg
    Scheveningseweg is a major historic road in The Hague, Netherlands, connecting the city center with the seaside district of Scheveningen.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da6274c58c81909c646eabed6f4f30 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e67170aa248190922fc845d2265ae3 completed April 20, 2026, 6:33 p.m.
Created at: April 11, 2026, 11:40 p.m.