Triple

T26498974
Position Surface form Disambiguated ID Type / Status
Subject Old Rhine region E669363 entity
Predicate contains P35 FINISHED
Object Koudekerk aan den Rijn
Koudekerk aan den Rijn is a village in South Holland, Netherlands, situated along the Old Rhine and known for its historic church and traditional Dutch riverside landscape.
E2292770 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: Koudekerk aan den Rijn | Statement: [Old Rhine region, contains, Koudekerk aan den Rijn]
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: Koudekerk aan den Rijn
Triple: [Old Rhine region, contains, Koudekerk aan den Rijn]
Generated description
Koudekerk aan den Rijn is a village in South Holland, Netherlands, situated along the Old Rhine and known for its historic church and traditional Dutch riverside 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_69eeb319007081909642b414b114b35a completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f61358da60819085a4be177f30ac99 completed May 2, 2026, 3:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7a1ef9b2fc819095a4e7dc2a4d789b completed Aug. 10, 2026, 6:56 p.m.
NEDg Description generation batch_6a7a1fc527cc81909994b786fb21c1d2 completed Aug. 10, 2026, 7 p.m.
NED2 Entity disambiguation (via description) batch_6a7a20958de481909d41f9a1bee9f738 completed Aug. 10, 2026, 7:03 p.m.
Created at: April 27, 2026, 1:11 a.m.