Triple
T32386063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chu Commandery |
E827547
|
entity |
| Predicate | hasTypeOfRebellion |
P171716
|
FINISHED |
| Object | anti-Qin peasant uprisings |
—
|
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: anti-Qin peasant uprisings | Statement: [Chu Commandery, hasTypeOfRebellion, anti-Qin peasant uprisings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfRebellion Context triple: [Chu Commandery, hasTypeOfRebellion, anti-Qin peasant uprisings]
-
A.
facedRebellionBy
Indicates that an entity experienced opposition or an uprising initiated by another entity.
-
B.
actsOfRebellion
chosen
Indicates actions that deliberately oppose, resist, or defy an established authority, rule, or controlling force.
-
C.
holderRebelledAgainst
Indicates that the holder engaged in rebellion or uprising against the referenced entity.
-
D.
hasCenterOfUprising
Indicates that a location serves as the main focal point or hub where an uprising or rebellion is centered or originates.
-
E.
rebellionOccurredAfter
Indicates that the rebellion took place later in time than the referenced event or situation.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 1, 2026, 12:51 a.m.