Triple
T26405105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Dongxing |
E663810
|
entity |
| Predicate | commanderForEasternWu |
P160580
|
FINISHED |
| Object | Zhuge Ke |
—
|
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: Zhuge Ke | Statement: [Battle of Dongxing, commanderForEasternWu, Zhuge Ke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderForEasternWu Context triple: [Battle of Dongxing, commanderForEasternWu, Zhuge Ke]
-
A.
ChineseCommander
Indicates that an individual holds a commander role within a Chinese military or armed forces context.
-
B.
EasternWuForces
chosen
Indicates a relationship where military forces are associated with, belong to, or act on behalf of the state or faction of Eastern Wu.
-
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.
commanderJapan
Indicates that an entity serves as the military commander of Japan or of Japanese forces.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 11:34 p.m.