Triple

T29427088
Position Surface form Disambiguated ID Type / Status
Subject Místek E746324 entity
Predicate isDistrictOf P22582 FINISHED
Object Frýdek-Místek
Frýdek-Místek is a city in the Moravian-Silesian Region of the Czech Republic, formed by the merger of the towns of Frýdek and Místek and serving as an important local industrial and administrative center.
E203586 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: Frýdek-Místek | Statement: [Místek, isDistrictOf, Frýdek-Místek]
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: Frýdek-Místek
Triple: [Místek, isDistrictOf, Frýdek-Místek]
Generated description
Frýdek-Místek is a city in the Moravian-Silesian Region of the Czech Republic, formed by the merger of the towns of Frýdek and Místek and serving as an important local industrial and administrative 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_69f0a7a06e0081908add494075912eb4 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f66ac6dc04819084203f8a4b51e676 completed May 2, 2026, 9:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a438a27783481908df1696aa7f7af5d completed June 30, 2026, 9:19 a.m.
NEDg Description generation batch_6a438b5d9c608190a33ffed9b9ff805e completed June 30, 2026, 9:24 a.m.
NED2 Entity disambiguation (via description) batch_6a438bd204e08190a4ed75eecc35868f completed June 30, 2026, 9:26 a.m.
Created at: April 28, 2026, 3:10 p.m.