Triple

T20596550
Position Surface form Disambiguated ID Type / Status
Subject Zavitinsky District E506062 entity
Predicate hasBorderWith P224 FINISHED
Object Tambovsky District
Tambovsky District is an administrative district (raion) in Amur Oblast, Russia, located in the southeastern part of the region near the border with China.
E1704962 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: Tambovsky District | Statement: [Zavitinsky District, hasBorderWith, Tambovsky 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: Tambovsky District
Triple: [Zavitinsky District, hasBorderWith, Tambovsky District]
Generated description
Tambovsky District is an administrative district (raion) in Amur Oblast, Russia, located in the southeastern part of the region near the border with China.

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_69e0b4ba6ae88190af871e1f9522c704 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6aa1bea1c81908b85f38b2a471285 completed April 20, 2026, 10:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1107344f7c8190bb8d4b75d68cb669 completed May 23, 2026, 1:47 a.m.
NEDg Description generation batch_6a110a2092e08190a0449f88ae116299 completed May 23, 2026, 2 a.m.
NED2 Entity disambiguation (via description) batch_6a110b07ed44819083f71d43b4811cfe completed May 23, 2026, 2:03 a.m.
Created at: April 16, 2026, 11:40 a.m.