Triple

T36813493
Position Surface form Disambiguated ID Type / Status
Subject Prince-Bishop of Wrocław E909659 entity
Predicate officeHolder P537 FINISHED
Object Karl von Österreich
Karl von Österreich was an 18th-century Habsburg archduke who served as a high-ranking Catholic prelate and political figure in Central Europe.
E332782 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 von Österreich | Statement: [Prince-Bishop of Wrocław, officeHolder, Karl von Österreich]
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 von Österreich
Triple: [Prince-Bishop of Wrocław, officeHolder, Karl von Österreich]
Generated description
Karl von Österreich was an 18th-century Habsburg archduke who served as a high-ranking Catholic prelate and political figure in Central Europe.

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_69f76e7cbbf48190891227b14d041139 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7ca6ff9c4819093b5c3eb668ec7de completed May 3, 2026, 10:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3e8c1d8a848190a969affefe6df4b7 completed June 26, 2026, 2:26 p.m.
NEDg Description generation batch_6a3e9d44e5388190857e6bc064ea4db9 completed June 26, 2026, 3:39 p.m.
NED2 Entity disambiguation (via description) batch_6a3ecab15dc08190b842d6b00cdb08d7 completed June 26, 2026, 6:53 p.m.
Created at: May 3, 2026, 4:13 p.m.