Triple
T36173928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li Jinglong |
E1046522
|
entity |
| Predicate | roleInJingnanCampaign |
P144300
|
FINISHED |
| Object | commander of imperial 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: commander of imperial forces | Statement: [Li Jinglong, roleInJingnanCampaign, commander of imperial forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInJingnanCampaign Context triple: [Li Jinglong, roleInJingnanCampaign, commander of imperial forces]
-
A.
sideInBattleOfYiling
Indicates that an entity participated as a side or faction in the Battle of Yiling.
-
B.
LaterJinCommander
Indicates that a person held a commanding or leadership role within the military forces of the Later Jin dynasty.
-
C.
ChineseCommander
chosen
Indicates that an individual holds a commander role within a Chinese military or armed forces context.
-
D.
roleDuringSecondSinoJapaneseWar
Indicates the specific role, position, or function an entity held or performed during the Second Sino-Japanese War.
-
E.
Wang Ben
Indicates a relationship or action involving an entity named "Wang Ben," such as authorship, participation, or association, depending on the specific context in which the predicate is used.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a017969ff908190a7a1a46b3f5ae362 |
completed | May 11, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a017609ff4c8190aba8a1864d39a608 |
completed | May 11, 2026, 6:24 a.m. |
Created at: May 3, 2026, 4:08 p.m.