Triple

T25072482
Position Surface form Disambiguated ID Type / Status
Subject Bilzen E627953 entity
Predicate hasNearbyAttraction P2064 FINISHED
Object Alden Biesen Castle
Alden Biesen Castle is a historic moated castle and former Teutonic Order commandery in Bilzen, Belgium, known for its impressive architecture, gardens, and cultural events.
E1667376 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: Alden Biesen Castle | Statement: [Bilzen, hasNearbyAttraction, Alden Biesen Castle]
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: Alden Biesen Castle
Triple: [Bilzen, hasNearbyAttraction, Alden Biesen Castle]
Generated description
Alden Biesen Castle is a historic moated castle and former Teutonic Order commandery in Bilzen, Belgium, known for its impressive architecture, gardens, and cultural events.

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_69e2ff2d71dc8190b4758e57d643cbe4 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f45d15ff608190b0e2b223c82d20e7 completed May 1, 2026, 7:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a105cebb2a0819097c2aa68c434a2a8 completed May 22, 2026, 1:40 p.m.
NEDg Description generation batch_6a105e32237c8190ba397b04b9692e7b completed May 22, 2026, 1:46 p.m.
NED2 Entity disambiguation (via description) batch_6a105ef626c08190933088d575b2e923 completed May 22, 2026, 1:49 p.m.
Created at: April 18, 2026, 6:17 a.m.