Triple

T6952539
Position Surface form Disambiguated ID Type / Status
Subject Amstel E160962 entity
Predicate hasBridge P386 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: [Amstel, hasBridge, Magere Brug]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Magere Brug
Context triple: [Amstel, hasBridge, 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. Oudekerksbrug
    Oudekerksbrug is a historic canal bridge in Amsterdam’s old city center, closely associated with the medieval Oude Kerk and the surrounding Red Light District.
  • E. Geeuwenbrug
    Geeuwenbrug is a small village in the Dutch province of Drenthe, situated within the municipality of Westerveld.
  • 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_69c68850419081909fb426b8f5a304c7 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dab18d648190a2f238fce3e59365 completed March 27, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7587ee1b08190b9f53ab7df4a4a58 completed March 28, 2026, 4:26 a.m.
Created at: March 27, 2026, 2:29 p.m.