Triple

T22296818
Position Surface form Disambiguated ID Type / Status
Subject Battle of Cudnów E551142 entity
Predicate locatedIn P40 FINISHED
Object Cudnów
Cudnów is a historical locality in present-day Ukraine, known primarily as the site of a significant 1660 battle during the Polish–Lithuanian Commonwealth’s conflicts with Muscovy and Cossack forces.
E1929879 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: Cudnów | Statement: [Battle of Cudnów, locatedIn, Cudnów]
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: Cudnów
Triple: [Battle of Cudnów, locatedIn, Cudnów]
Generated description
Cudnów is a historical locality in present-day Ukraine, known primarily as the site of a significant 1660 battle during the Polish–Lithuanian Commonwealth’s conflicts with Muscovy and Cossack forces.

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_69e11e45fb848190a1b2ae21296e3a5f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15720fba0819080f6c96f6df4f1e0 completed April 29, 2026, 12:56 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2898afbcac819090a462e0ddb1dc56 completed June 9, 2026, 10:50 p.m.
NEDg Description generation batch_6a289987c9988190a355050ae3113a08 completed June 9, 2026, 10:53 p.m.
NED2 Entity disambiguation (via description) batch_6a289d68dafc8190a4624b6bc4f54b9c completed June 9, 2026, 11:10 p.m.
Created at: April 16, 2026, 8:41 p.m.