Triple

T28370881
Position Surface form Disambiguated ID Type / Status
Subject Willich E718624 entity
Predicate coatOfArms P1663 FINISHED
Object Coat of arms of Willich
The Coat of arms of Willich is the official heraldic emblem of the German town of Willich in North Rhine-Westphalia, symbolizing its local history and identity.
E1816366 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: Coat of arms of Willich | Statement: [Willich, coatOfArms, Coat of arms of Willich]
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: Coat of arms of Willich
Triple: [Willich, coatOfArms, Coat of arms of Willich]
Generated description
The Coat of arms of Willich is the official heraldic emblem of the German town of Willich in North Rhine-Westphalia, symbolizing its local history and identity.

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_69eff6ee5afc8190bd7375a29f0cc6c6 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64c5a4ae881909f323fda31d41148 completed May 2, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1632fc7cd8819092b74d1798e87079 completed May 26, 2026, 11:55 p.m.
NEDg Description generation batch_6a1633c829e88190a174f35400af8d84 completed May 26, 2026, 11:59 p.m.
NED2 Entity disambiguation (via description) batch_6a1634ca88388190880255bb6d4fbe41 completed May 27, 2026, 12:03 a.m.
Created at: April 28, 2026, 12:59 a.m.