Triple
T25232361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakatiya Kala Thoranam |
E632247
|
entity |
| Predicate | linkedDynastyCapital |
P123151
|
FINISHED |
| Object | Orugallu (Warangal) |
—
|
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: Orugallu (Warangal) | Statement: [Kakatiya Kala Thoranam, linkedDynastyCapital, Orugallu (Warangal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDynastyCapital Context triple: [Kakatiya Kala Thoranam, linkedDynastyCapital, Orugallu (Warangal)]
-
A.
associatedDynastyCapital
chosen
Indicates a relationship where a dynasty is linked to the city that served as its capital.
-
B.
belongsToDynasticHistory
Indicates that something is part of, or associated with, a particular dynastic historical period or lineage.
-
C.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
D.
regionOfDynasty
Indicates the geographic region or area in which a given dynasty held power or was primarily based.
-
E.
lastReigningDynastyOf
Indicates that one dynasty is the final ruling dynasty to have governed a particular political entity or territory.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:06 p.m.