Triple

T23003080
Position Surface form Disambiguated ID Type / Status
Subject Grote Kerk (Edam) E572683 entity
Predicate locatedIn P40 FINISHED
Object Edam NE NERFINISHED

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: Edam | Statement: [Grote Kerk (Edam), locatedIn, Edam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edam
Context triple: [Grote Kerk (Edam), locatedIn, Edam]
  • A. Edam chosen
    Edam is a historic Dutch town in North Holland, internationally known for its namesake Edam cheese and traditional cheese markets.
  • B. 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.
  • C. Gouda
    Gouda is a historic Dutch city renowned worldwide for its namesake cheese, traditional cheese market, and well-preserved medieval architecture.
  • D. 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.
  • E. Beemster cheese
    Beemster cheese is a traditional Dutch Gouda-style cheese known for its rich, nutty flavor and production from milk sourced in the Beemster polder region of the Netherlands.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245b6a3ac81908087599eefe3e365 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f183549bdc81908fdcd44e2c92f7c4 completed April 29, 2026, 4:04 a.m.
Created at: April 17, 2026, 3:50 p.m.