Triple

T28335158
Position Surface form Disambiguated ID Type / Status
Subject Prague-East District E717648 entity
Predicate contains P35 FINISHED
Object Sedlec (Prague-East)
Sedlec (Prague-East) is a small municipality and village located in the Prague-East District of the Central Bohemian Region in the Czech Republic.
E1816982 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: Sedlec (Prague-East) | Statement: [Prague-East District, contains, Sedlec (Prague-East)]
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: Sedlec (Prague-East)
Triple: [Prague-East District, contains, Sedlec (Prague-East)]
Generated description
Sedlec (Prague-East) is a small municipality and village located in the Prague-East District of the Central Bohemian Region in the Czech Republic.

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_69eff6e9a57c8190a69c2c74b5d72119 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64bd515048190a935a0a579b55299 completed May 2, 2026, 7:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1632f6b93c8190b28b287b9eeeb497 completed May 26, 2026, 11:55 p.m.
NEDg Description generation batch_6a163583272081908b5d1ef8ebd3f89f completed May 27, 2026, 12:06 a.m.
NED2 Entity disambiguation (via description) batch_6a1637d205508190bd347bfc224a9427 completed May 27, 2026, 12:16 a.m.
Created at: April 28, 2026, 12:35 a.m.