Triple
T8407338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhou Yu |
E198531
|
entity |
| Predicate | roleInBattleOfRedCliffs |
P28183
|
FINISHED |
| Object | co-commander of allied forces |
—
|
LITERAL FINISHED |
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: co-commander of allied forces | Statement: [Zhou Yu, roleInBattleOfRedCliffs, co-commander of allied forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfRedCliffs Context triple: [Zhou Yu, roleInBattleOfRedCliffs, co-commander of allied forces]
-
A.
sideInBattleOfYiling
Indicates that an entity participated as a side or faction in the Battle of Yiling.
-
B.
notableBattleRole
chosen
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
C.
roleInGallicWars
Indicates the role or involvement an entity had in the events or campaigns of the Gallic Wars.
-
D.
notableCommanderSide
Indicates that a particular military or strategic side is notably commanded or led by a specified commander.
-
E.
roleDuringSecondSinoJapaneseWar
Indicates the specific role, position, or function an entity held or performed during the Second Sino-Japanese War.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb831409308190981089c303ebaef4 |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.