Triple

T3124242
Position Surface form Disambiguated ID Type / Status
Subject Hendrick de Keyser E65257 entity
Predicate notableWork P4 FINISHED
Object Munttoren E24383 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: Munttoren | Statement: [Hendrick de Keyser, notableWork, Munttoren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Munttoren
Context triple: [Hendrick de Keyser, notableWork, 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. Schmalzturm
    Schmalzturm is a historic medieval tower in the Bavarian town of Landsberg am Lech, notable as a landmark of its old town fortifications.
  • C. Storvreten
    Storvreten is a residential locality within Botkyrka Municipality in the Stockholm County area of Sweden.
  • D. Mönch
    Mönch is a prominent mountain peak in the Swiss Bernese Alps, forming part of the famous Eiger–Mönch–Jungfrau trio.
  • E. Ouvrage Oberheid
    Ouvrage Oberheid is a small Maginot Line fortification in northeastern France that formed part of the defensive network protecting the Thionville sector before and during World War II.
  • 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_69ad8580c72481909672d37acf647893 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada52d856c8190a5d65b8a6452be21 completed March 8, 2026, 4:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69b20f72c2048190ab2aa40a109f5976 completed March 12, 2026, 12:57 a.m.
Created at: March 8, 2026, 3:04 p.m.