Triple

T30602243
Position Surface form Disambiguated ID Type / Status
Subject Mělník District E778940 entity
Predicate containsSettlement P847 FINISHED
Object Kostelec nad Labem
Kostelec nad Labem is a small historic town in the Central Bohemian Region of the Czech Republic, situated northeast of Prague on the Elbe River.
E2287033 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: Kostelec nad Labem | Statement: [Mělník District, containsSettlement, Kostelec nad Labem]
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: Kostelec nad Labem
Triple: [Mělník District, containsSettlement, Kostelec nad Labem]
Generated description
Kostelec nad Labem is a small historic town in the Central Bohemian Region of the Czech Republic, situated northeast of Prague on the Elbe River.

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_69f224a21fc08190abd9d8dd9eb6bb4c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f689b36a888190b139d35c8c5d88bd completed May 2, 2026, 11:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4756b7565c81908c86b6eadf00642a completed July 3, 2026, 6:29 a.m.
NEDg Description generation batch_6a4757ab61fc8190afaddd24e84be636 completed July 3, 2026, 6:33 a.m.
NED2 Entity disambiguation (via description) batch_6a47583de450819085171db142fd6c80 completed July 3, 2026, 6:35 a.m.
Created at: April 29, 2026, 8:25 p.m.