Triple

T35727385
Position Surface form Disambiguated ID Type / Status
Subject Konrad V Kantner E1032651 entity
Predicate regionRuled P15936 FINISHED
Object Głogów region
The Głogów region is a historical area in southwestern Poland centered around the town of Głogów, known for its medieval Silesian heritage and shifting political rule.
E2288011 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: Głogów region | Statement: [Konrad V Kantner, regionRuled, Głogów region]
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: Głogów region
Triple: [Konrad V Kantner, regionRuled, Głogów region]
Generated description
The Głogów region is a historical area in southwestern Poland centered around the town of Głogów, known for its medieval Silesian heritage and shifting political rule.

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_69f76e102b5881909e5d63a30a5cecbe completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a131fc3881909d9897e52ca4f546 completed May 3, 2026, 7:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5a5ad1cf488190bb2e70306892bb3e completed July 17, 2026, 4:39 p.m.
NEDg Description generation batch_6a5a5b5b11b08190b56754ee3c918272 completed July 17, 2026, 4:42 p.m.
NED2 Entity disambiguation (via description) batch_6a5a5baee3ec8190bd079436e0d2d9ad completed July 17, 2026, 4:43 p.m.
Created at: May 3, 2026, 4:05 p.m.