Triple

T36725036
Position Surface form Disambiguated ID Type / Status
Subject Viceroy of Liangjiang E907171 entity
Predicate region P40 FINISHED
Object Liangjiang
Liangjiang was a major administrative region in imperial China that encompassed the provinces of Jiangsu, Jiangxi, and often Anhui, overseen by the powerful Viceroy of Liangjiang.
E2279360 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: Liangjiang | Statement: [Viceroy of Liangjiang, region, Liangjiang]
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: Liangjiang
Triple: [Viceroy of Liangjiang, region, Liangjiang]
Generated description
Liangjiang was a major administrative region in imperial China that encompassed the provinces of Jiangsu, Jiangxi, and often Anhui, overseen by the powerful Viceroy of Liangjiang.

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_69f76e746e4c8190a0d05cc6d57a643e completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c89fdf2c819082e11a2172bcb9ab completed May 3, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41fd3e466481908340ec289ebc4491 completed June 29, 2026, 5:06 a.m.
NEDg Description generation batch_6a41fe15cf208190bfed180870ce5f5a completed June 29, 2026, 5:09 a.m.
NED2 Entity disambiguation (via description) batch_6a41fe9b3eb08190a237473926405b04 completed June 29, 2026, 5:11 a.m.
Created at: May 3, 2026, 4:12 p.m.