Triple

T26143875
Position Surface form Disambiguated ID Type / Status
Subject Tavda E659596 entity
Predicate administrativeCenterOf P383 FINISHED
Object Tavdinsky District
Tavdinsky District is an administrative district in Sverdlovsk Oblast, Russia, known for its center in the town of Tavda and its location in the forested Ural region.
E2040497 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: Tavdinsky District | Statement: [Tavda, administrativeCenterOf, Tavdinsky District]
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: Tavdinsky District
Triple: [Tavda, administrativeCenterOf, Tavdinsky District]
Generated description
Tavdinsky District is an administrative district in Sverdlovsk Oblast, Russia, known for its center in the town of Tavda and its location in the forested Ural region.

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_69ee5bc496a88190af7deb7ab5e081de completed April 26, 2026, 6:39 p.m.
NER Named-entity recognition batch_69f60be6f3e88190b22dfb8b2c802f46 completed May 2, 2026, 2:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a35259777808190a989f4dc3f43e419 completed June 19, 2026, 11:18 a.m.
NEDg Description generation batch_6a35268520f881909b265b5ea58f2b9b completed June 19, 2026, 11:22 a.m.
NED2 Entity disambiguation (via description) batch_6a3529902ecc8190837433ab0a0f7348 completed June 19, 2026, 11:35 a.m.
Created at: April 26, 2026, 8:21 p.m.