Triple

T34243235
Position Surface form Disambiguated ID Type / Status
Subject Spišská Nová Ves District E878524 entity
Predicate contains P35 FINISHED
Object Jamník (Spišská Nová Ves District)
Jamník (Spišská Nová Ves District) is a small village and municipality in the Košice Region of eastern Slovakia.
E2087443 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: Jamník (Spišská Nová Ves District) | Statement: [Spišská Nová Ves District, contains, Jamník (Spišská Nová Ves District)]
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: Jamník (Spišská Nová Ves District)
Triple: [Spišská Nová Ves District, contains, Jamník (Spišská Nová Ves District)]
Generated description
Jamník (Spišská Nová Ves District) is a small village and municipality in the Košice Region of eastern Slovakia.

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_69f349b3618481909df955b063f305b2 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71280295c81909a2fcda9df66c359 completed May 3, 2026, 9:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36d5ed9ffc8190b0ffd99890153bba completed June 20, 2026, 6:03 p.m.
NEDg Description generation batch_6a36d6d3b04c8190819ff0e1f74f6fbf completed June 20, 2026, 6:07 p.m.
NED2 Entity disambiguation (via description) batch_6a36d762832481909d8ca24e737396af completed June 20, 2026, 6:09 p.m.
Created at: May 1, 2026, 1:56 a.m.