Triple
T7730617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viranarasimha Raya |
E175239
|
entity |
| Predicate | associatedDynastyPhase |
P45085
|
FINISHED |
| Object | Tuluva expansion period |
—
|
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: Tuluva expansion period | Statement: [Viranarasimha Raya, associatedDynastyPhase, Tuluva expansion period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDynastyPhase Context triple: [Viranarasimha Raya, associatedDynastyPhase, Tuluva expansion period]
-
A.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
B.
associatedWithDynastyPolitics
Indicates a relationship where an entity is involved in, influenced by, or connected to the political activities, power structures, or governance associated with a particular dynasty.
-
C.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
D.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
E.
dynasticContext
chosen
Indicates the historical or political circumstances defined by a particular ruling dynasty under which the related entities or events are situated.
- 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7074eca4c8190bd51fd1b450729e8 |
completed | March 27, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69c7016a6cf88190b53bf4b958f0f302 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:06 p.m.