Triple

T27473691
Position Surface form Disambiguated ID Type / Status
Subject Zaraysk E693391 entity
Predicate governedAs P1715 FINISHED
Object Zaraysk Urban Settlement
Zaraysk Urban Settlement is a municipal formation in Moscow Oblast, Russia, that encompasses the town of Zaraysk and is responsible for its local self-government.
E1789121 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: Zaraysk Urban Settlement | Statement: [Zaraysk, governedAs, Zaraysk Urban Settlement]
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: Zaraysk Urban Settlement
Triple: [Zaraysk, governedAs, Zaraysk Urban Settlement]
Generated description
Zaraysk Urban Settlement is a municipal formation in Moscow Oblast, Russia, that encompasses the town of Zaraysk and is responsible for its local self-government.

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_69ef538105548190a771cc5a0cf8c211 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62e422e7c8190a256e3155a22ba27 completed May 2, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12ec9338308190b64557357700b95f completed May 24, 2026, 12:18 p.m.
NEDg Description generation batch_6a12ee3f436c8190b1daf7ec5041304e completed May 24, 2026, 12:25 p.m.
NED2 Entity disambiguation (via description) batch_6a12eef54e2c8190b9e8d589f036b066 completed May 24, 2026, 12:28 p.m.
Created at: April 27, 2026, 12:55 p.m.