Triple

T37389168
Position Surface form Disambiguated ID Type / Status
Subject Opperman E928656 entity
Predicate hasVariant P455 FINISHED
Object Oppermann
Oppermann is a surname of German origin borne by various notable individuals in fields such as politics, academia, and the arts.
E2224749 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: Oppermann | Statement: [Opperman, hasVariant, Oppermann]
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: Oppermann
Triple: [Opperman, hasVariant, Oppermann]
Generated description
Oppermann is a surname of German origin borne by various notable individuals in fields such as politics, academia, and the arts.

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_69f76ebb10c481909b54b9dba263e29f completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb8d3696c08190925d7135fa5107d6 completed May 6, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40770166248190996f7595806b2489 completed June 28, 2026, 1:21 a.m.
NEDg Description generation batch_6a40777f8658819086f67175409b28fa completed June 28, 2026, 1:23 a.m.
NED2 Entity disambiguation (via description) batch_6a407806efbc81909b322cc504066e01 completed June 28, 2026, 1:25 a.m.
Created at: May 3, 2026, 4:16 p.m.