Triple
T36890386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tailapa-deva |
E911730
|
entity |
| Predicate | capitalAssociatedWithDynasty |
P180697
|
FINISHED |
| Object | Kalyani |
—
|
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 | Statement: [Tailapa-deva, capitalAssociatedWithDynasty, Kalyani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalAssociatedWithDynasty Context triple: [Tailapa-deva, capitalAssociatedWithDynasty, Kalyani]
-
A.
associatedDynastyCapital
Indicates a relationship where a dynasty is linked to the city that served as its capital.
-
B.
capitalDuringReign
Indicates that a particular city or location served as the capital of a political entity during the reign of a specified ruler.
-
C.
hasCapitalInDynasty
chosen
Indicates that a particular city or location served as the capital during a specified dynasty or historical ruling period.
-
D.
prominentDynasty
Indicates that a dynasty holds significant historical, political, or cultural importance relative to other dynasties.
-
E.
rulingDynasties
Indicates that one entity served as the ruling dynasty governing or controlling another entity (such as a state, region, or polity) during a particular historical period.
- 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_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:13 p.m.