Triple
T28076114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Northern Expedition |
E709546
|
entity |
| Predicate | commanderForShuHan |
P68449
|
FINISHED |
| Object | Zhuge Liang |
—
|
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 Liang | Statement: [First Northern Expedition, commanderForShuHan, Zhuge Liang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderForShuHan Context triple: [First Northern Expedition, commanderForShuHan, Zhuge Liang]
-
A.
commanderForCaoWei
Indicates that one entity served as a military commander on behalf of, or in the service of, the state of Cao Wei.
-
B.
ChineseCommander
Indicates that an individual holds a commander role within a Chinese military or armed forces context.
-
C.
EasternWuForces
Indicates a relationship where military forces are associated with, belong to, or act on behalf of the state or faction of Eastern Wu.
-
D.
ShuForces
Indicates a relationship where forces or military units are associated with, belong to, or act on behalf of the Shu faction or state.
-
E.
sideCommander
chosen
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 8:49 p.m.