Triple

T12163194
Position Surface form Disambiguated ID Type / Status
Subject Vredenburgkade E289760 entity
Predicate partOf P40 FINISHED
Object Vredenburg area E954416 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: Vredenburg area | Statement: [Vredenburgkade, partOf, Vredenburg area]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vredenburg area
Context triple: [Vredenburgkade, partOf, Vredenburg area]
  • A. Vredenburg
    Vredenburg is a town on South Africa’s West Coast that serves as a regional commercial and service hub near Saldanha Bay.
  • B. Vredenburg chosen
    Vredenburg is a former name of the Muziekcentrum Vredenburg, a prominent concert and music venue in Utrecht, Netherlands.
  • C. Drusberg area
    The Drusberg area is a mountainous region in the Swiss Alps known for its rugged terrain and alpine landscapes.
  • D. Oudezijds Kolk area
    The Oudezijds Kolk area is a historic canal-side quarter in Amsterdam’s old city center, known for its narrow waterways, centuries-old buildings, and proximity to the Red Light District.
  • E. Zeeburg district
    Zeeburg district is a former borough in the eastern part of Amsterdam, Netherlands, known for its mix of historic harbor areas and modern residential developments.
  • 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_69d6ab4d6c00819095a9a7c35de83cfb completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915c498a081908389598d0c247505 completed April 10, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f6a0baf0819094e90b7e92b979d4 completed May 2, 2026, 1:05 p.m.
Created at: April 8, 2026, 9:50 p.m.