Triple

T6302885
Position Surface form Disambiguated ID Type / Status
Subject Willemsbrug E141296 entity
Predicate hasLocalName P6353 FINISHED
Object Willemsbrug E141296 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: Willemsbrug | Statement: [Willemsbrug, hasLocalName, Willemsbrug]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Willemsbrug
Context triple: [Willemsbrug, hasLocalName, Willemsbrug]
  • A. Willemsbrug chosen
    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.
  • B. Paddepoelsterbrug
    Paddepoelsterbrug is a bridge in the city of Groningen in the Netherlands, known for carrying local traffic across the Van Starkenborghkanaal.
  • C. Geeuwenbrug
    Geeuwenbrug is a small village in the Dutch province of Drenthe, situated within the municipality of Westerveld.
  • D. Waalbrug
    Waalbrug is a historic steel arch bridge over the River Waal in Nijmegen, the Netherlands, known for its distinctive design and key role in World War II.
  • E. Torensluis bridge
    Torensluis bridge is a historic and unusually wide 17th-century stone bridge in Amsterdam, built on the Singel canal where the Jan Roodenpoortstoren tower once stood.
  • 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_69c008cf0ad4819095def81e2bd42f9f completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0645e150881908b49a07914dcbfd8 completed March 22, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c603fb43688190839af2ffea45df90 completed March 27, 2026, 4:13 a.m.
Created at: March 22, 2026, 4:27 p.m.