Triple

T26359534
Position Surface form Disambiguated ID Type / Status
Subject Bitwa pod Kockiem E660161 entity
Predicate place P373 FINISHED
Object Lubelszczyzna
Lubelszczyzna is a historical and geographical region in eastern Poland, centered around the city of Lublin and known for its cultural heritage and agricultural landscapes.
E1830375 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: Lubelszczyzna | Statement: [Bitwa pod Kockiem, place, Lubelszczyzna]
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: Lubelszczyzna
Triple: [Bitwa pod Kockiem, place, Lubelszczyzna]
Generated description
Lubelszczyzna is a historical and geographical region in eastern Poland, centered around the city of Lublin and known for its cultural heritage and agricultural landscapes.

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_69ee8126d52c8190bc0b34337c2c9aa8 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60ff21bc08190994f406feb484aad completed May 2, 2026, 2:53 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1ccf08ca6081909f7294dc073f7136 completed June 1, 2026, 12:15 a.m.
NEDg Description generation batch_6a1ccff86fc88190b1438e77f3a5f101 completed June 1, 2026, 12:19 a.m.
NED2 Entity disambiguation (via description) batch_6a249466d5b08190bd3886ef517cb367 completed June 6, 2026, 9:43 p.m.
Created at: April 26, 2026, 10:50 p.m.