Triple
T17268139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahendradatta |
E419181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Isyana dynasty member |
C37999
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Isyana dynasty member Context triple: [Mahendradatta, instanceOf, Isyana dynasty member]
-
A.
Salian dynasty member
A Salian dynasty member is an individual belonging to the German royal and imperial family that ruled the Holy Roman Empire from 1024 to 1125, originating from the Frankish nobility along the Rhine.
-
B.
Sailendra dynasty member
chosen
A Sailendra dynasty member is an individual belonging to the influential Buddhist ruling family that dominated parts of Java and Sumatra in Southeast Asia between the 8th and 9th centuries, known for monumental architecture like Borobudur and extensive maritime trade.
-
C.
member of the Battiad dynasty
A member of the Battiad dynasty is an individual belonging to the royal lineage that ruled the ancient Greek city-state of Cyrene in North Africa, traditionally founded by Battus I and his descendants.
-
D.
member of the Lodi dynasty
A member of the Lodi dynasty is an individual belonging to the Afghan-origin ruling family that controlled the Delhi Sultanate in northern India during the late 15th and early 16th centuries.
-
E.
Gediminid dynasty member
A Gediminid dynasty member is an individual descended from or belonging to the medieval ruling house founded by Grand Duke Gediminas, which governed the Grand Duchy of Lithuania and its successor states.
- F. None of above.
Provenance (1 batch)
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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.