Triple
T32386034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dazexiang |
E827546
|
entity |
| Predicate | uprisingTarget |
P4698
|
FINISHED |
| Object | Qin dynasty |
—
|
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: Qin dynasty | Statement: [Dazexiang, uprisingTarget, Qin dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uprisingTarget Context triple: [Dazexiang, uprisingTarget, Qin dynasty]
-
A.
uprising
chosen
Indicates a collective act of resistance or rebellion by a group against an established authority or ruling power.
-
B.
uprisingPlannedAt
Indicates that a planned uprising or rebellion is scheduled to occur at a specific location or time.
-
C.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
D.
motiveForUprising
Indicates that a particular factor, condition, or event serves as a motivating cause or justification for an uprising or rebellion.
-
E.
uprisingDate
Indicates the date on which an uprising or rebellion occurred or began.
- 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_69f6c1d26e608190abfa275a4c02a3ce |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:51 a.m.