Triple

T6153945
Position Surface form Disambiguated ID Type / Status
Subject Edam E137272 entity
Predicate knownFor P22 FINISHED
Object Edam cheese E572682 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: Edam cheese | Statement: [Edam, knownFor, Edam cheese]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edam cheese
Context triple: [Edam, knownFor, Edam cheese]
  • A. Edam cheese chosen
    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.
  • B. 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.
  • C. Gouda
    Gouda is a historic Dutch city renowned worldwide for its namesake cheese, traditional cheese market, and well-preserved medieval architecture.
  • D. Edam
    Edam is a historic Dutch town in North Holland, internationally known for its namesake Edam cheese and traditional cheese markets.
  • E. Comté cheese
    Comté cheese is a traditional French cow’s milk cheese from the Jura region, known for its firm texture, complex nutty flavor, and long aging process.
  • 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_69c008a45d008190832a9e19f5d63406 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05cffc7bc819092633a9e5f1abe2f completed March 22, 2026, 9:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c16ed4abc88190993cfd4ef4f2862e completed March 23, 2026, 4:48 p.m.
Created at: March 22, 2026, 4:17 p.m.