Triple
T27074746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushyabhuti dynasty |
E685425
|
entity |
| Predicate | contemporaryDynasty |
P6542
|
FINISHED |
| Object | Maukharis |
—
|
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: Maukharis | Statement: [Pushyabhuti dynasty, contemporaryDynasty, Maukharis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryDynasty Context triple: [Pushyabhuti dynasty, contemporaryDynasty, Maukharis]
-
A.
contemporaryDynastyInSouth
Indicates that a dynasty existed in the same general historical period as a reference dynasty and was located in the southern region relative to that reference.
-
B.
contemporary
chosen
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
C.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
D.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
E.
dynastyContext
Indicates the historical or cultural dynasty within which an entity, event, or relationship is situated or contextualized.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 8:30 a.m.