Triple

T36656527
Position Surface form Disambiguated ID Type / Status
Subject Johann Ludwig von Wallmoden-Gimborn E905007 entity
Predicate givenName P17 FINISHED
Object Johann Ludwig
Johann Ludwig is the given name of Johann Ludwig von Wallmoden-Gimborn, an 18th-century German nobleman and art collector associated with the Hanoverian court.
E2214358 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: Johann Ludwig | Statement: [Johann Ludwig von Wallmoden-Gimborn, givenName, Johann Ludwig]
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: Johann Ludwig
Triple: [Johann Ludwig von Wallmoden-Gimborn, givenName, Johann Ludwig]
Generated description
Johann Ludwig is the given name of Johann Ludwig von Wallmoden-Gimborn, an 18th-century German nobleman and art collector associated with the Hanoverian court.

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_69f76e6e3b908190970251b30f76ad71 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c777e924819081a6634f549fe552 completed May 3, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3f69f4c3ac819080c235a50a030c68 completed June 27, 2026, 6:13 a.m.
NEDg Description generation batch_6a3f6ad89c6c81908b2526a3098c3a12 completed June 27, 2026, 6:16 a.m.
NED2 Entity disambiguation (via description) batch_6a3f6b57be6c819080ba84bcb71ec152 completed June 27, 2026, 6:19 a.m.
Created at: May 3, 2026, 4:11 p.m.