Triple

T27227965
Position Surface form Disambiguated ID Type / Status
Subject municipality of Bergen, North Holland E682068 entity
Predicate hasSettlement P1068 FINISHED
Object Egmond-Binnen
Egmond-Binnen is a village in the Dutch province of North Holland, known for its historic Benedictine abbey and coastal dune landscape.
E2144788 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: Egmond-Binnen | Statement: [municipality of Bergen, North Holland, hasSettlement, Egmond-Binnen]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Egmond-Binnen
Triple: [municipality of Bergen, North Holland, hasSettlement, Egmond-Binnen]
Generated description
Egmond-Binnen is a village in the Dutch province of North Holland, known for its historic Benedictine abbey and coastal dune landscape.

Provenance (5 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_69eefacdad7881908b7bca61c90a1a1e completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f6264bcdc08190b0860b3015aac6c6 completed May 2, 2026, 4:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a384a0f2bc08190b147cee2abfba125 completed June 21, 2026, 8:31 p.m.
NEDg Description generation batch_6a384ba60c048190b1d4ce4e32b70873 completed June 21, 2026, 8:37 p.m.
NED2 Entity disambiguation (via description) batch_6a384c058ea48190811335ddfc72be5c completed June 21, 2026, 8:39 p.m.
Created at: April 27, 2026, 9:45 a.m.