Triple

T24072812
Position Surface form Disambiguated ID Type / Status
Subject Ústí nad Labem District E596280 entity
Predicate contains P35 FINISHED
Object Řehlovice
Řehlovice is a small municipality and village in the Ústí nad Labem Region of the Czech Republic, known for its rural character and proximity to the regional city of Ústí nad Labem.
E1634183 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: Řehlovice | Statement: [Ústí nad Labem District, contains, Řehlovice]
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: Řehlovice
Triple: [Ústí nad Labem District, contains, Řehlovice]
Generated description
Řehlovice is a small municipality and village in the Ústí nad Labem Region of the Czech Republic, known for its rural character and proximity to the regional city of Ústí nad Labem.

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_69e288c3999c8190809b282a04813dec completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1db1aad248190a1d25c64cc5016eb completed April 29, 2026, 10:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fe33bcc088190b5d063bbbfa97116 completed May 22, 2026, 5:01 a.m.
NEDg Description generation batch_6a0fe516b4c48190aa24a16a0b1e1d5e completed May 22, 2026, 5:09 a.m.
NED2 Entity disambiguation (via description) batch_6a0fe5d61ffc819090ded9351ea9066d completed May 22, 2026, 5:12 a.m.
Created at: April 17, 2026, 10:42 p.m.