Triple
T36217085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siyaka II |
E1047727
|
entity |
| Predicate | successorDynastyStrengthened |
P202158
|
FINISHED |
| Object | Paramara dynasty |
—
|
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: Paramara dynasty | Statement: [Siyaka II, successorDynastyStrengthened, Paramara dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynastyStrengthened Context triple: [Siyaka II, successorDynastyStrengthened, Paramara dynasty]
-
A.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
-
B.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
C.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
-
D.
successorDynastyContinuity
Indicates that one dynasty directly continues or succeeds another in a continuous line of rule or authority.
-
E.
successorDynastyDeFacto
Indicates that one dynasty effectively functioned as the successor to another in practice, regardless of formal or legally recognized succession.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
| PDg | Predicate description generation | batch_6a005b2cdbc881908b433623e3252df5 |
completed | May 10, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:09 p.m.