Triple

T8995513
Position Surface form Disambiguated ID Type / Status
Subject Boskoop E214895 entity
Predicate locatedBetween P1262 FINISHED
Object Gouda E70496 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: Gouda | Statement: [Boskoop, locatedBetween, Gouda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gouda
Context triple: [Boskoop, locatedBetween, Gouda]
  • A. Gouda
    Gouda is a small town in South Africa’s Western Cape province, known for its rural setting amid farmlands and nearby mountain wilderness areas.
  • B. Gouda chosen
    Gouda is a historic Dutch city renowned worldwide for its namesake cheese, traditional cheese market, and well-preserved medieval architecture.
  • C. Maasdam cheese
    Maasdam cheese is a Dutch semi-hard cow's milk cheese similar to Swiss Emmental, known for its large holes, sweet nutty flavor, and good melting properties.
  • D. Edam cheese
    Edam cheese is a semi-hard Dutch cheese, traditionally sold in red wax-coated spheres, known for its mild, slightly nutty flavor and good keeping qualities.
  • E. Edam
    Edam is a historic Dutch town in North Holland, internationally known for its namesake Edam cheese and traditional cheese markets.
  • 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_69ca83a05c608190bdfdbdb25e994b39 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc68ddff288190869731df2c178ff6 completed April 1, 2026, 12:37 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfd0d0e6a08190a2faf4157b8a9cd4 completed April 3, 2026, 2:38 p.m.
Created at: March 30, 2026, 7:04 p.m.