Triple

T34917565
Position Surface form Disambiguated ID Type / Status
Subject Effner E1007045 entity
Predicate hasNotableBearer P458 FINISHED
Object Karl Effner
Karl Effner was a 19th-century German landscape architect best known for designing and remodeling several royal gardens in Bavaria, including parts of the grounds at Nymphenburg Palace.
E2164221 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 Effner | Statement: [Effner, hasNotableBearer, Karl Effner]
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 Effner
Triple: [Effner, hasNotableBearer, Karl Effner]
Generated description
Karl Effner was a 19th-century German landscape architect best known for designing and remodeling several royal gardens in Bavaria, including parts of the grounds at Nymphenburg Palace.

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_69f76dc2b6b0819095a61debbd405269 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f782161fec81908a5e16e8abd2401a completed May 3, 2026, 5:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38bfbaa8308190ab1a9b415ec7b9c5 completed June 22, 2026, 4:53 a.m.
NEDg Description generation batch_6a38c040b0788190883524c26fb778fd completed June 22, 2026, 4:55 a.m.
NED2 Entity disambiguation (via description) batch_6a38c075cb388190858dd0e7ace83c5e completed June 22, 2026, 4:56 a.m.
Created at: May 3, 2026, 4 p.m.