Triple
T32852051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lý Cao Tông |
E840276
|
entity |
| Predicate | causeOfDynasticDecline |
P26452
|
FINISHED |
| Object | court corruption |
—
|
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: court corruption | Statement: [Lý Cao Tông, causeOfDynasticDecline, court corruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDynasticDecline Context triple: [Lý Cao Tông, causeOfDynasticDecline, court corruption]
-
A.
dynastyDissolutionCause
Indicates the reason or factor that led to the dissolution or end of a dynasty.
-
B.
causeOfDownfall
chosen
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
C.
historicalPeriodOfDecline
Indicates that an entity corresponds to a historical period characterized by decline or deterioration in another entity’s power, influence, stability, or prosperity.
-
D.
dynasticPurpose
Indicates that an action, decision, or arrangement is undertaken primarily to advance, secure, or perpetuate a ruling family’s lineage, power, or succession.
-
E.
dynasticStructure
Indicates the hierarchical organization and succession relationships within a dynasty or ruling family.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:17 a.m.