Triple
T26405180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liang dynasty |
E663811
|
entity |
| Predicate | dynasticCyclePhase |
P162155
|
FINISHED |
| Object | Southern dynasties |
—
|
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: Southern dynasties | Statement: [Liang dynasty, dynasticCyclePhase, Southern dynasties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticCyclePhase Context triple: [Liang dynasty, dynasticCyclePhase, Southern dynasties]
-
A.
successorDynasticPhase
Indicates that one dynastic phase directly follows and replaces another in a historical or genealogical sequence.
-
B.
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.
-
C.
dynasticNumber
Indicates the ordinal position or identifying number assigned to a dynasty within a historical or genealogical sequence.
-
D.
dynasticState
Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
-
E.
dynastyChange
Indicates a transition in ruling power from one dynasty to another.
- F. None of above. chosen
Provenance (4 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 26, 2026, 11:34 p.m.