Triple

T2317402
Position Surface form Disambiguated ID Type / Status
Subject Amsterdam-Centrum E51096 entity
Predicate contains P35 FINISHED
Object Begijnhof E232581 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: Begijnhof | Statement: [Amsterdam-Centrum, contains, Begijnhof]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Begijnhof
Context triple: [Amsterdam-Centrum, contains, Begijnhof]
  • A. Begijnhof chosen
    Begijnhof is a historic, secluded courtyard in central Amsterdam known for its preserved medieval houses and former beguine community.
  • B. Bullewijk
    Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
  • C. Hendrik-Ido-Ambacht
    Hendrik-Ido-Ambacht is a town and municipality in the western Netherlands known for its residential character and location within the Rotterdam metropolitan area.
  • D. Bloemendaal
    Bloemendaal is a coastal municipality in North Holland, Netherlands, known for its beaches, dunes, and affluent residential areas.
  • E. Oldenzaal
    Oldenzaal is a historic city in the eastern Netherlands known for its medieval center and location near the German border in the province of Overijssel.
  • 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_69a88b074b908190ae983dbca7757d88 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc62df2048190ac7a5ebc0a4139b2 completed March 7, 2026, 6:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69af653ce900819097157ca76cb45a81 completed March 10, 2026, 12:26 a.m.
Created at: March 4, 2026, 7:49 p.m.