Triple

T22169751
Position Surface form Disambiguated ID Type / Status
Subject Kumul Rebellion E547887 entity
Predicate location P40 FINISHED
Object Kumul Prefecture
Kumul Prefecture is an administrative region in eastern Xinjiang, China, centered on the oasis city of Hami and historically significant as a frontier area along the Silk Road.
E2297581 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: Kumul Prefecture | Statement: [Kumul Rebellion, location, Kumul Prefecture]
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: Kumul Prefecture
Triple: [Kumul Rebellion, location, Kumul Prefecture]
Generated description
Kumul Prefecture is an administrative region in eastern Xinjiang, China, centered on the oasis city of Hami and historically significant as a frontier area along the Silk Road.

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_69e11e3c4c5c81908d336165816b12e0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a67f4dc81909cc5f8d2c1fe6129 completed April 28, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a83aa9abcec8190a59100a29e071686 completed Aug. 18, 2026, 12:43 a.m.
NEDg Description generation batch_6a83ab3fd2f881909405866502d827f7 completed Aug. 18, 2026, 12:45 a.m.
NED2 Entity disambiguation (via description) batch_6a83ab8fe5d4819082bee9a5086c4165 completed Aug. 18, 2026, 12:47 a.m.
Created at: April 16, 2026, 8:34 p.m.