Triple
T28952348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ningyuan |
E731050
|
entity |
| Predicate | MingCommander |
P144300
|
FINISHED |
| Object | Yuan Chonghuan |
—
|
NE NERFINISHED |
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: Yuan Chonghuan | Statement: [Battle of Ningyuan, MingCommander, Yuan Chonghuan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MingCommander Context triple: [Battle of Ningyuan, MingCommander, Yuan Chonghuan]
-
A.
ChineseCommander
chosen
Indicates that an individual holds a commander role within a Chinese military or armed forces context.
-
B.
Wang Ben
Indicates a relationship or action involving an entity named "Wang Ben," such as authorship, participation, or association, depending on the specific context in which the predicate is used.
-
C.
BaekjeCommander
Indicates that one entity serves as a military commander or leader associated with the Baekje kingdom.
-
D.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
-
E.
firstEmperorToRuleAllChina
Indicates that the subject was the earliest emperor to unify and govern all of China under a single centralized rule.
- F. None of above.
Provenance (3 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65bb90db08190ba3b036e9b923906 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:44 a.m.