Triple

T34887599
Position Surface form Disambiguated ID Type / Status
Subject Mecklenburg E1006189 entity
Predicate namedAfter P63 FINISHED
Object Castle of Mecklenburg
The Castle of Mecklenburg is a historic medieval fortress in northern Germany that served as the ancestral seat of the House of Mecklenburg and gave its name to the surrounding region.
E2117461 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: Castle of Mecklenburg | Statement: [Mecklenburg, namedAfter, Castle of Mecklenburg]
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: Castle of Mecklenburg
Triple: [Mecklenburg, namedAfter, Castle of Mecklenburg]
Generated description
The Castle of Mecklenburg is a historic medieval fortress in northern Germany that served as the ancestral seat of the House of Mecklenburg and gave its name to the surrounding region.

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_69f76dbedb288190afe5780710847410 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f781bb99288190ad583d967b52b225 completed May 3, 2026, 5:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3786de303081909146f6e84160d67e completed June 21, 2026, 6:38 a.m.
NEDg Description generation batch_6a378b22fc4c8190ac64a3eebb895c30 completed June 21, 2026, 6:56 a.m.
NED2 Entity disambiguation (via description) batch_6a378be274988190ae88ccba1185a813 completed June 21, 2026, 6:59 a.m.
Created at: May 3, 2026, 4 p.m.