Triple
T9916990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qin Er Shi |
E185893
|
entity |
| Predicate | causeOfDynastyFall |
P26452
|
FINISHED |
| Object | harsh rule and heavy taxation |
—
|
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: harsh rule and heavy taxation | Statement: [Qin Er Shi, causeOfDynastyFall, harsh rule and heavy taxation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDynastyFall Context triple: [Qin Er Shi, causeOfDynastyFall, harsh rule and heavy taxation]
-
A.
causeOfDownfall
chosen
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
B.
endCauseOfRevolt
Indicates that the subject is the cause or factor that brings a revolt or uprising to an end.
-
C.
reasonForLossOfImperialStatus
Indicates the cause or circumstance that led to an entity losing its imperial status.
-
D.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
-
E.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb540195881908f25f7dde5c66a75 |
completed | April 2, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:42 p.m.