Triple

T30411979
Position Surface form Disambiguated ID Type / Status
Subject Beguinage of Bruges E773644 entity
Predicate locatedNear P294 FINISHED
Object Minnewater Lake
Minnewater Lake is a picturesque, tranquil lake in Bruges, Belgium, often called the “Lake of Love” and known for its romantic scenery and historic surroundings.
E1914432 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: Minnewater Lake | Statement: [Beguinage of Bruges, locatedNear, Minnewater Lake]
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: Minnewater Lake
Triple: [Beguinage of Bruges, locatedNear, Minnewater Lake]
Generated description
Minnewater Lake is a picturesque, tranquil lake in Bruges, Belgium, often called the “Lake of Love” and known for its romantic scenery and historic surroundings.

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_69f22490b8b48190ab10c886a8d58c89 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68646a420819096f45e8c037f8ac8 completed May 2, 2026, 11:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2798af7460819085eb85d40e55d154 completed June 9, 2026, 4:38 a.m.
NEDg Description generation batch_6a279a025d0481909e5d9eea25f94b47 completed June 9, 2026, 4:43 a.m.
NED2 Entity disambiguation (via description) batch_6a279aaa7f48819093ec1b953b8d9792 completed June 9, 2026, 4:46 a.m.
Created at: April 29, 2026, 8:05 p.m.