Triple

T26021673
Position Surface form Disambiguated ID Type / Status
Subject Mirow Castle E647164 entity
Predicate locatedInMunicipality P40 FINISHED
Object town of Mirow
The town of Mirow is a small municipality in the Mecklenburg Lake District of northeastern Germany, known for its picturesque lakeside setting and historic Mirow Castle.
E1705199 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: town of Mirow | Statement: [Mirow Castle, locatedInMunicipality, town of Mirow]
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: town of Mirow
Triple: [Mirow Castle, locatedInMunicipality, town of Mirow]
Generated description
The town of Mirow is a small municipality in the Mecklenburg Lake District of northeastern Germany, known for its picturesque lakeside setting and historic Mirow Castle.

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_69e77e8aa65881909ca58918f29ab2a0 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f605e5af4081909e3862d44e313d7f completed May 2, 2026, 2:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1107a913908190b0888d14a799a770 completed May 23, 2026, 1:49 a.m.
NEDg Description generation batch_6a110a2092e08190a0449f88ae116299 completed May 23, 2026, 2 a.m.
NED2 Entity disambiguation (via description) batch_6a110b07ed44819083f71d43b4811cfe completed May 23, 2026, 2:03 a.m.
Created at: April 22, 2026, 9:04 a.m.