Triple
T34613803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeng Guofan |
E888807
|
entity |
| Predicate | roleInTaipingRebellion |
P88009
|
FINISHED |
| Object | commander of Qing 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 Qing forces | Statement: [Zeng Guofan, roleInTaipingRebellion, commander of Qing forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTaipingRebellion Context triple: [Zeng Guofan, roleInTaipingRebellion, commander of Qing forces]
-
A.
roleInRevolt
chosen
Indicates the specific function, position, or level of participation an entity had within a particular revolt or uprising.
-
B.
roleInMexicanWarOfIndependence
Indicates the specific part or function an entity played in the events or efforts of the Mexican War of Independence.
-
C.
roleDuringSecondSinoJapaneseWar
Indicates the specific role, position, or function an entity held or performed during the Second Sino-Japanese War.
-
D.
roleDuringRussianCivilWar
Indicates the specific function, position, or involvement an entity had during the period of the Russian Civil War.
-
E.
roleInManchuria
Indicates that an entity holds or held a specific role, position, or function in the context of Manchuria.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00d24043e8819090cc473b6c0923d0 |
completed | May 10, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_6a00d1ec12fc81908c514ed088ef8300 |
completed | May 10, 2026, 6:43 p.m. |
Created at: May 1, 2026, 2:03 a.m.