Triple
T28948000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peroz I |
E730930
|
entity |
| Predicate | successorAsKingOfKings |
P195444
|
FINISHED |
| Object | Balash |
—
|
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: Balash | Statement: [Peroz I, successorAsKingOfKings, Balash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsKingOfKings Context triple: [Peroz I, successorAsKingOfKings, Balash]
-
A.
successorAsTitularKing
Indicates that one entity becomes the next holder of a ceremonial or nominal kingship position previously held by another entity.
-
B.
successorAsEasternRuler
Indicates that one entity became the next ruler of an eastern domain or territory after another entity.
-
C.
successorAsDeFactoRuler
Indicates that one entity becomes the next actual (though not necessarily officially recognized) ruler after another entity.
-
D.
successorAsPrince
Indicates that one individual directly follows another in holding the title or role of prince.
-
E.
successorAsRegent
Indicates that one entity assumes the role of regent following another, serving as their successor in that governing capacity.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: April 28, 2026, 8:41 a.m.