Triple

T30966441
Position Surface form Disambiguated ID Type / Status
Subject Tirlemont E788970 entity
Predicate hasLandmark P105 FINISHED
Object Tienen sugar refinery
Tienen sugar refinery is a major Belgian sugar production plant in Tienen, known as one of the country’s most prominent industrial landmarks.
E1940482 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: Tienen sugar refinery | Statement: [Tirlemont, hasLandmark, Tienen sugar refinery]
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: Tienen sugar refinery
Triple: [Tirlemont, hasLandmark, Tienen sugar refinery]
Generated description
Tienen sugar refinery is a major Belgian sugar production plant in Tienen, known as one of the country’s most prominent industrial landmarks.

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_69f224c3a6b48190951add9b7b7f0271 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6938596a4819088301e25e753a4db completed May 3, 2026, 12:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a28fbb864d8819085f76da2dac6970f completed June 10, 2026, 5:52 a.m.
NEDg Description generation batch_6a28fc4803108190abbd7012f4736854 completed June 10, 2026, 5:55 a.m.
NED2 Entity disambiguation (via description) batch_6a28fcf2bad08190ac49847b725fc2c8 completed June 10, 2026, 5:58 a.m.
Created at: April 29, 2026, 8:54 p.m.