Triple

T27481324
Position Surface form Disambiguated ID Type / Status
Subject Battle of Kunyang E693611 entity
Predicate conflictOf P12 FINISHED
Object Han–Xin War
The Han–Xin War was a pivotal military campaign during China’s early Han dynasty, marked by decisive battles that helped consolidate imperial power after the fall of the Qin.
 E1774505 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: Han–Xin War | Statement: [Battle of Kunyang, conflictOf, Han–Xin War]
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: Han–Xin War
Triple: [Battle of Kunyang, conflictOf, Han–Xin War]
Generated description
The Han–Xin War was a pivotal military campaign during China’s early Han dynasty, marked by decisive battles that helped consolidate imperial power after the fall of the Qin.

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_69ef5381f2648190a2392d0fab833095 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62e47d5148190bff308cf49612191 completed May 2, 2026, 5:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12bbeae0fc81908c07b9039738622a completed May 24, 2026, 8:50 a.m.
NEDg Description generation batch_6a12bc771b0481909cca1c87c805f0de completed May 24, 2026, 8:53 a.m.
NED2 Entity disambiguation (via description) batch_6a12bd3f12b481908606b8e373ff408a completed May 24, 2026, 8:56 a.m.
Created at: April 27, 2026, 12:59 p.m.