Triple

T32967928
Position Surface form Disambiguated ID Type / Status
Subject Bad Landeck E843425 entity
Predicate hasAlternativeName P39 FINISHED
Object Landeck i. Schl. (historical abbreviation)
Landeck i. Schl. is a historical abbreviation for Bad Landeck, a spa town now known as Lądek-Zdrój in southwestern Poland.
E2030655 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: Landeck i. Schl. (historical abbreviation) | Statement: [Bad Landeck, hasAlternativeName, Landeck i. Schl. (historical abbreviation)]
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: Landeck i. Schl. (historical abbreviation)
Triple: [Bad Landeck, hasAlternativeName, Landeck i. Schl. (historical abbreviation)]
Generated description
Landeck i. Schl. is a historical abbreviation for Bad Landeck, a spa town now known as Lądek-Zdrój in southwestern Poland.

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_69f3494b9fc48190bb61c955ba471275 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d1a5e6a881908df6ec45496a8d1d completed May 3, 2026, 4:40 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34d28087a881909a00e64dfb81140b completed June 19, 2026, 5:24 a.m.
NEDg Description generation batch_6a34d30d5a7c8190b05f04ed591361b0 completed June 19, 2026, 5:26 a.m.
NED2 Entity disambiguation (via description) batch_6a34d405a48c8190ab95daacc1a06ff5 completed June 19, 2026, 5:30 a.m.
Created at: May 1, 2026, 1:21 a.m.