Triple

T26325225
Position Surface form Disambiguated ID Type / Status
Subject Istebna E662232 entity
Predicate nearbySettlement P350 FINISHED
Object Jaworzynka
Jaworzynka is a village in southern Poland’s Silesian Voivodeship, known as one of the three closely linked highland settlements in the Istebna region near the Slovak and Czech borders.
E2282949 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: Jaworzynka | Statement: [Istebna, nearbySettlement, Jaworzynka]
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: Jaworzynka
Triple: [Istebna, nearbySettlement, Jaworzynka]
Generated description
Jaworzynka is a village in southern Poland’s Silesian Voivodeship, known as one of the three closely linked highland settlements in the Istebna region near the Slovak and Czech borders.

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_69ee812f32748190871d970c4e2a8ddf completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60f2f31288190b6b6318edad4baba completed May 2, 2026, 2:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a42340d6c508190a2b6170ddbc6874a completed June 29, 2026, 8:59 a.m.
NEDg Description generation batch_6a4234bc63ec819092ce911a963a7ff0 completed June 29, 2026, 9:02 a.m.
NED2 Entity disambiguation (via description) batch_6a4236bcf5588190b22327a92c70d411 completed June 29, 2026, 9:11 a.m.
Created at: April 26, 2026, 10:30 p.m.