Triple
T19638903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vakataka period |
E471475
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Pravarapura |
—
|
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: Pravarapura | Statement: [Vakataka period, capital, Pravarapura]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pravarapura Context triple: [Vakataka period, capital, Pravarapura]
-
A.
Pravarapura
chosen
Pravarapura was an ancient city in central India that served as a major political and cultural center under the Vakataka dynasty.
-
B.
Valmikinagar
Valmikinagar is a town in Bihar, India, known for its proximity to the Valmiki Tiger Reserve and its location along the Gandak River near the Indo-Nepal border.
-
C.
Dahanapura
Dahanapura was the principal city and political center of the historical Kediri Kingdom in Java.
-
D.
Rajapur
Rajapur is a town in the Chitrakoot district of Uttar Pradesh, India, known for its religious significance and proximity to sites associated with the epic Ramayana.
-
E.
Mahadevapura
Mahadevapura is a rapidly developing residential and commercial neighborhood in eastern Bengaluru, India, known for its proximity to major IT parks and tech hubs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641090c408190b2adb8a6abf1b4c9 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:44 p.m.