Triple
T32689087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shu forces |
E835805
|
entity |
| Predicate | laterChiefStrategist |
P95168
|
FINISHED |
| Object | Jiang Wan |
—
|
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: Jiang Wan | Statement: [Shu forces, laterChiefStrategist, Jiang Wan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterChiefStrategist Context triple: [Shu forces, laterChiefStrategist, Jiang Wan]
-
A.
chiefStrategist
Indicates that one entity serves as the primary planner and director of strategy for another entity.
-
B.
predecessorAsChiefStrategist
Indicates that one entity previously held the role of chief strategist before another entity in a sequence of officeholders.
-
C.
chiefLieutenantOf
Indicates that one person serves as the primary subordinate or top-ranking assistant to another leader or authority figure.
-
D.
laterLeader
chosen
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
E.
laterCaptain
Indicates that one entity becomes the captain of something at a later time than another referenced captain or captaincy.
- 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_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: May 1, 2026, 1:09 a.m.