Triple

T36995646
Position Surface form Disambiguated ID Type / Status
Subject Eitorf E915220 entity
Predicate hasTwinTown P919 FINISHED
Object Moravská Třebová
Moravská Třebová is a historic town in the Pardubice Region of the Czech Republic, known for its well-preserved Renaissance architecture and former importance as a regional cultural center.
E2293159 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: Moravská Třebová | Statement: [Eitorf, hasTwinTown, Moravská Třebová]
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: Moravská Třebová
Triple: [Eitorf, hasTwinTown, Moravská Třebová]
Generated description
Moravská Třebová is a historic town in the Pardubice Region of the Czech Republic, known for its well-preserved Renaissance architecture and former importance as a regional cultural center.

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_69f76e8f1a8c81909db172ed31304971 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9ffe1027c8190b098337a60324e80 completed May 5, 2026, 2:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7a6e1622088190a654c8f6ecf20276 completed Aug. 11, 2026, 12:34 a.m.
NEDg Description generation batch_6a7a6ed7b9dc8190a937cd583129fd0d completed Aug. 11, 2026, 12:37 a.m.
NED2 Entity disambiguation (via description) batch_6a7a6f1d73a8819084bbfad8c3278fef completed Aug. 11, 2026, 12:38 a.m.
Created at: May 3, 2026, 4:14 p.m.