Triple
T29970016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wang Xianzhi |
E761289
|
entity |
| Predicate | typeOfRebellion |
P143788
|
FINISHED |
| Object | large-scale agrarian uprising |
—
|
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: large-scale agrarian uprising | Statement: [Wang Xianzhi, typeOfRebellion, large-scale agrarian uprising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRebellion Context triple: [Wang Xianzhi, typeOfRebellion, large-scale agrarian uprising]
-
A.
actsOfRebellion
Indicates actions that deliberately oppose, resist, or defy an established authority, rule, or controlling force.
-
B.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
C.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
D.
typeOfInsurgency
Indicates the specific kind or category of insurgency that characterizes a given conflict or group.
-
E.
typeOfUprisingLed
chosen
Indicates the specific kind or category of uprising that a leader was responsible for directing or organizing.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: April 29, 2026, 6:31 p.m.