Triple
T27074703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumaragupta III |
E685424
|
entity |
| Predicate | reignPhase |
P66246
|
FINISHED |
| Object | declining phase of the Gupta Empire |
—
|
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: declining phase of the Gupta Empire | Statement: [Kumaragupta III, reignPhase, declining phase of the Gupta Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignPhase Context triple: [Kumaragupta III, reignPhase, declining phase of the Gupta Empire]
-
A.
reignStatus
chosen
Indicates the status or condition of an entity’s period of rule or governance, such as whether it is ongoing, completed, or otherwise characterized.
-
B.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
C.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
D.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
E.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 8:30 a.m.