Triple

T6553329
Position Surface form Disambiguated ID Type / Status
Subject Zeewolde E152380 entity
Predicate borderedBy P224 FINISHED
Object Putten E349805 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: Putten | Statement: [Zeewolde, borderedBy, Putten]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Putten
Context triple: [Zeewolde, borderedBy, Putten]
  • A. Putten chosen
    Putten is a town and municipality in the province of Gelderland in the central Netherlands, known for its rural character and World War II history.
  • B. Hampoort
    Hampoort is a historic city gate, likely part of the old fortifications of a European town or city.
  • C. Winschoten
    Winschoten is a town in the northeast of the Netherlands known historically as a regional trade center and for its traditional windmills and Jewish heritage.
  • D. Heverlee
    Heverlee is a suburb of Leuven in the Flemish Brabant province of Belgium, known for its residential areas, green spaces, and nearby university facilities.
  • E. Kippen
    Kippen is a small village in the Stirling council area of central Scotland, known for its rural setting and views towards the Trossachs.
  • 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_69c688058d6881908c19b309cc55dbfa completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae0847d88190b38f9d7dba0faae1 completed March 27, 2026, 4:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cb8041d081909cd64dab7ccbd035 completed March 27, 2026, 6:25 p.m.
Created at: March 27, 2026, 1:51 p.m.