Triple

T1614775
Position Surface form Disambiguated ID Type / Status
Subject Blauwbrug E34690 entity
Predicate hasViewOf P854 FINISHED
Object Magere Brug E34074 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: Magere Brug | Statement: [Blauwbrug, hasViewOf, Magere Brug]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Magere Brug
Context triple: [Blauwbrug, hasViewOf, Magere Brug]
  • A. Magere Brug chosen
    Magere Brug is a historic and picturesque white wooden drawbridge in Amsterdam, renowned as one of the city's most iconic canal crossings.
  • B. Amsterdamse Brug
    Amsterdamse Brug is a bridge in Amsterdam that spans the Weespertrekvaart canal, serving as a local traffic connection in the eastern part of the city.
  • C. Blauwbrug
    Blauwbrug is a historic, ornately decorated bridge in central Amsterdam, known for its theatrical, Parisian-style design and its role as a prominent crossing over the Amstel River.
  • D. Kinkerbrug
    Kinkerbrug is a bridge in Amsterdam that spans the Kostverlorenvaart canal, connecting parts of the city's Oud-West area.
  • E. Willemsbrug
    Willemsbrug is a prominent red steel cable-stayed bridge in Rotterdam, Netherlands, spanning the Nieuwe Maas and connecting the city’s northern and southern banks.
  • 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_69a885ffc5ec819091afa325d5f9611c completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9098f384c81909ef836ee779466e2 completed March 5, 2026, 4:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad58c6d7e88190b9fc0e34a007a2f5 completed March 8, 2026, 11:08 a.m.
Created at: March 4, 2026, 7:28 p.m.