Triple

T5878114
Position Surface form Disambiguated ID Type / Status
Subject World Conference Center Bonn E130675 entity
Predicate architect P184 FINISHED
Object Heinrich Wörner
Heinrich Wörner is a German architect best known for designing the World Conference Center Bonn, a major international conference venue in Bonn, Germany.
E2297427 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: Heinrich Wörner | Statement: [World Conference Center Bonn, architect, Heinrich Wörner]
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: Heinrich Wörner
Triple: [World Conference Center Bonn, architect, Heinrich Wörner]
Generated description
Heinrich Wörner is a German architect best known for designing the World Conference Center Bonn, a major international conference venue in Bonn, Germany.

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_69c0085523688190bfd487479ce819e6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03630eefc8190ad1aaa1919ecf97f completed March 22, 2026, 6:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a837e5f418c8190a5c4a45a2101baa7 completed Aug. 17, 2026, 9:34 p.m.
NEDg Description generation batch_6a837ed03fac81908608f1560545707d completed Aug. 17, 2026, 9:36 p.m.
NED2 Entity disambiguation (via description) batch_6a837f211d5081909cd564bc92de540e completed Aug. 17, 2026, 9:37 p.m.
Created at: March 22, 2026, 3:57 p.m.