Triple

T25315013
Position Surface form Disambiguated ID Type / Status
Subject Karl Johann von Königsmarck E634711 entity
Predicate givenName P17 FINISHED
Object Karl Johann
Karl Johann was a 17th-century Swedish nobleman and military officer from the influential Königsmarck family, known for his involvement in European court intrigues.
E1763014 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 Johann | Statement: [Karl Johann von Königsmarck, givenName, Karl Johann]
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 Johann
Triple: [Karl Johann von Königsmarck, givenName, Karl Johann]
Generated description
Karl Johann was a 17th-century Swedish nobleman and military officer from the influential Königsmarck family, known for his involvement in European court intrigues.

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_69e75a9847c08190bb02990d06d5ffb7 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f49688f3b881909a7bb16aeea95fbe completed May 1, 2026, 12:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12623e73ec81908eca8d3f74874997 completed May 24, 2026, 2:28 a.m.
NEDg Description generation batch_6a126440683881909b462092139a79cf completed May 24, 2026, 2:36 a.m.
NED2 Entity disambiguation (via description) batch_6a1264a5d7748190902dbe10317c00a8 completed May 24, 2026, 2:38 a.m.
Created at: April 21, 2026, 1:27 p.m.