Triple
T17850617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gao Zhan |
E445792
|
entity |
| Predicate | causeOfDynasticWeakening |
P125302
|
FINISHED |
| Object | 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: heavy taxation | Statement: [Gao Zhan, causeOfDynasticWeakening, heavy taxation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDynasticWeakening Context triple: [Gao Zhan, causeOfDynasticWeakening, heavy taxation]
-
A.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
B.
dynastyDissolutionCause
chosen
Indicates the reason or factor that led to the dissolution or end of a dynasty.
-
C.
dynasticOutcome
Indicates the result or consequence of a succession or transfer of power within a dynasty, such as continuation, change, or end of a ruling line.
-
D.
dynasticUse
Indicates the use of something (such as a name, title, symbol, or resource) in a way that is tied to or characteristic of a particular dynasty or ruling family.
-
E.
dynastyAffected
Indicates that a particular dynasty is influenced, impacted, or changed in some way by another entity, event, or condition.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffe415c8190aed351c52b78a143 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.