Triple

T32893908
Position Surface form Disambiguated ID Type / Status
Subject Shpola E841412 entity
Predicate administrativeCenterOf P383 FINISHED
Object Shpola Raion
Shpola Raion was a former administrative district (raion) in Cherkasy Oblast, central Ukraine, known for its agricultural landscape and governance centered in the town of Shpola.
E2035372 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: Shpola Raion | Statement: [Shpola, administrativeCenterOf, Shpola Raion]
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: Shpola Raion
Triple: [Shpola, administrativeCenterOf, Shpola Raion]
Generated description
Shpola Raion was a former administrative district (raion) in Cherkasy Oblast, central Ukraine, known for its agricultural landscape and governance centered in the town of Shpola.

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_69f34945ae408190b72d8118c83beb77 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d04489e0819096b47b87227ab434 completed May 3, 2026, 4:34 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34effd975c819087c3af0a9703842c completed June 19, 2026, 7:30 a.m.
NEDg Description generation batch_6a34fb0302d88190b0ae27220c8bd833 completed June 19, 2026, 8:17 a.m.
NED2 Entity disambiguation (via description) batch_6a34fb5f5a048190b29c2dca71573603 completed June 19, 2026, 8:18 a.m.
Created at: May 1, 2026, 1:18 a.m.