Triple

T34308651
Position Surface form Disambiguated ID Type / Status
Subject Reiss E880380 entity
Predicate hasNotableBearer P458 FINISHED
Object Karl Reiss
Karl Reiss is a notable individual who shares the surname Reiss, recognized as a distinguished bearer of that name.
E2222328 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: Karl Reiss | Statement: [Reiss, hasNotableBearer, Karl Reiss]
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: Karl Reiss
Triple: [Reiss, hasNotableBearer, Karl Reiss]
Generated description
Karl Reiss is a notable individual who shares the surname Reiss, recognized as a distinguished bearer of that name.

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_69f349b8bb6c8190ad12a7957a574f04 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71362f1448190985a80ce7af475cb completed May 3, 2026, 9:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a40636838e4819090536a5245e53ac5 completed June 27, 2026, 11:57 p.m.
NEDg Description generation batch_6a4064ff3f5c8190903b3c4ccf87b35d completed June 28, 2026, 12:04 a.m.
NED2 Entity disambiguation (via description) batch_6a406574585c8190a8d9f3565bdd46ea completed June 28, 2026, 12:06 a.m.
Created at: May 1, 2026, 1:57 a.m.