Triple
T36890449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalyani (Basavakalyan) |
E911731
|
entity |
| Predicate | linkedDynastyName |
P7426
|
FINISHED |
| Object | Kalyani Chalukyas |
—
|
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: Kalyani Chalukyas | Statement: [Kalyani (Basavakalyan), linkedDynastyName, Kalyani Chalukyas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDynastyName Context triple: [Kalyani (Basavakalyan), linkedDynastyName, Kalyani Chalukyas]
-
A.
dynasticallyLinkedTo
Indicates a relationship where two entities are connected through a line of succession, inheritance, or familial rule within or across dynasties.
-
B.
dynasticSurname
Indicates that the two entities share a family name associated with a particular dynasty or ruling lineage.
-
C.
associatedWithDynasty
chosen
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
D.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
E.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 3, 2026, 4:13 p.m.