Triple
T25296571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saluva dynasty |
E634231
|
entity |
| Predicate | dynasticChangeReason |
P125302
|
FINISHED |
| Object | internal turmoil in Vijayanagara Empire |
—
|
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: internal turmoil in Vijayanagara Empire | Statement: [Saluva dynasty, dynasticChangeReason, internal turmoil in Vijayanagara Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticChangeReason Context triple: [Saluva dynasty, dynasticChangeReason, internal turmoil in Vijayanagara Empire]
-
A.
dynasticNameChangeReason
Indicates the reason or cause for a change in a dynasty’s official name.
-
B.
dynasticSuccessionChangedBy
Indicates that a change or disruption has occurred in the established line of dynastic succession due to the influence or action of the related entity.
-
C.
dynastyChange
Indicates a transition in ruling power from one dynasty to another.
-
D.
dynasticNameChangedTo
Indicates that an entity’s dynastic name was replaced by or transitioned into a new dynastic name.
-
E.
dynastyDissolutionCause
chosen
Indicates the reason or factor that led to the dissolution or end of a dynasty.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd2e5ec8190965046138f838057 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.