Triple
T32689028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Changban |
E835804
|
entity |
| Predicate | commanderForLiuBei |
P68449
|
FINISHED |
| Object | Liu Bei |
—
|
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: Liu Bei | Statement: [Battle of Changban, commanderForLiuBei, Liu Bei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderForLiuBei Context triple: [Battle of Changban, commanderForLiuBei, Liu Bei]
-
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.
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.
-
D.
TexianCommander
Indicates that an entity serves as a military commander for Texian forces in a given context or event.
-
E.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:09 a.m.