Triple

T22071785
Position Surface form Disambiguated ID Type / Status
Subject De Munt E545424 entity
Predicate hasAlternativeName P39 FINISHED
Object Munttoren 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: Munttoren | Statement: [De Munt, hasAlternativeName, Munttoren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munttoren
Context triple: [De Munt, hasAlternativeName, Munttoren]
  • A. Munttoren chosen
    Munttoren is a historic clock and bell tower in central Amsterdam, originally part of the city’s medieval fortifications and now a notable canal-side landmark.
  • B. Speyetoren
    Speyetoren is one of the historic medieval Broel Towers in Kortrijk, Belgium, notable as a remnant of the city’s former fortifications.
  • C. Turretot
    Turretot is a small French commune in the Normandy region that forms part of the greater Le Havre metropolitan area.
  • D. Mützel
    Mützel is a village and district (Ortsteil) of the town of Genthin in the state of Saxony-Anhalt, Germany.
  • E. Schmalzturm
    Schmalzturm is a historic medieval tower in the Bavarian town of Landsberg am Lech, notable as a landmark of its old town fortifications.
  • 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_69e11e344dfc81909b1d88a7221329c7 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12888dcc08190b18d3d44d09ab943 completed April 28, 2026, 9:37 p.m.
Created at: April 16, 2026, 8:28 p.m.