Triple

T19208660
Position Surface form Disambiguated ID Type / Status
Subject Grote Markt, Haarlem E480300 entity
Predicate hasLandmark P105 FINISHED
Object Vleeshal 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: Vleeshal | Statement: [Grote Markt, Haarlem, hasLandmark, Vleeshal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vleeshal
Context triple: [Grote Markt, Haarlem, hasLandmark, Vleeshal]
  • A. Vleeshalle
    Vleeshalle is a historic former meat market building and notable architectural landmark located in the Belgian town of Veurne.
  • B. Vleeshal (Haarlem) chosen
    Vleeshal (Haarlem) is a historic former meat hall on Haarlem’s Grote Markt, now used as an exhibition space for contemporary art.
  • C. Ossenzijl
    Ossenzijl is a small village in the Dutch province of Overijssel, known as a gateway to the Weerribben-Wieden National Park and its extensive wetlands and waterways.
  • D. Bruls
    Bruls is a Dutch surname most notably borne by Hubert Bruls, a Dutch politician and long-serving mayor of Nijmegen.
  • E. Scherpenzeel
    Scherpenzeel is a small Dutch municipality in the province of Gelderland, known for its rural character and historic village center.
  • 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_69d8e8cb8c348190b52075823911c869 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5f9a000188190afb762ea24bc3deb completed April 20, 2026, 10:02 a.m.
Created at: April 10, 2026, 1:20 p.m.