Triple

T6441112
Position Surface form Disambiguated ID Type / Status
Subject Begijnhof entrance E138225 entity
Predicate locatedIn P40 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: [Begijnhof entrance, locatedIn, Begijnhof]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Begijnhof
Context triple: [Begijnhof entrance, locatedIn, Begijnhof]
  • A. Begijnhof chosen
    Begijnhof is a historic, secluded courtyard in central Amsterdam known for its preserved medieval houses and former beguine community.
  • B. Janskerkhof
    Janskerkhof is a historic square in the center of Utrecht, Netherlands, known for its weekly flower market and proximity to the former St. John's Church.
  • C. Bullewijk
    Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
  • D. Nijverdal
    Nijverdal is a town in the Dutch province of Overijssel known as a gateway to the Sallandse Heuvelrug National Park and its surrounding natural landscapes.
  • E. 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.
  • 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_69c008aa61ac8190bc96715ed79fe2d8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06968c6a88190a623da9bd3152a66 completed March 22, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8a1f26d948190b887c4ccc19548cc completed March 29, 2026, 3:52 a.m.
Created at: March 22, 2026, 4:46 p.m.