Triple
T7639635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandragupta I |
E172965
|
entity |
| Predicate | royalHouseFounder |
P77474
|
FINISHED |
| Object | early imperial phase of the Gupta dynasty |
—
|
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: early imperial phase of the Gupta dynasty | Statement: [Chandragupta I, royalHouseFounder, early imperial phase of the Gupta dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalHouseFounder Context triple: [Chandragupta I, royalHouseFounder, early imperial phase of the Gupta dynasty]
-
A.
firstMonarch
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
B.
founderOfPredecessor
Indicates that an entity is the founder of another entity that served as a predecessor to a specified organization or institution.
-
C.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
D.
monarchFather
Indicates that one entity is the male parent (father) of another entity in a monarchical or royal lineage.
-
E.
duchyFoundedBy
Indicates that a particular duchy was established or created by a specific person, group, or authority.
- F. None of above. chosen
Provenance (4 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6facc4b5481908697e662b0991e3f |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:57 p.m.