Triple
T28324582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liaodong campaign against Gongsun Yuan |
E717370
|
entity |
| Predicate | notableCommanderOnWeiSide |
P167088
|
FINISHED |
| Object | Sima Yi |
—
|
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: Sima Yi | Statement: [Liaodong campaign against Gongsun Yuan, notableCommanderOnWeiSide, Sima Yi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommanderOnWeiSide Context triple: [Liaodong campaign against Gongsun Yuan, notableCommanderOnWeiSide, Sima Yi]
-
A.
commanderForCaoWei
chosen
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.
commanderForCaoCao
Indicates that one entity serves as a military commander under the authority or command of Cao Cao.
-
D.
LaterJinCommander
Indicates that a person held a commanding or leadership role within the military forces of the Later Jin dynasty.
-
E.
notableCommanderSide
Indicates that a particular military or strategic side is notably commanded or led by a specified commander.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a00c486d394819084fe93d5bb11ea1e |
completed | May 10, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_6a00c39d99d48190a94bfa057213499c |
completed | May 10, 2026, 5:42 p.m. |
Created at: April 28, 2026, 12:27 a.m.