Triple
T17126749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rukn al-Dawla |
E415615
|
entity |
| Predicate | predecessorInJibal |
P113879
|
FINISHED |
| Object | local rulers of Jibal |
—
|
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: local rulers of Jibal | Statement: [Rukn al-Dawla, predecessorInJibal, local rulers of Jibal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInJibal Context triple: [Rukn al-Dawla, predecessorInJibal, local rulers of Jibal]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
bearerPredecessor
chosen
Indicates that one entity previously held a role, title, or position that is now held by another entity, establishing a predecessor-successor relationship between them.
-
C.
predecessorInMyth
Indicates that one mythological figure, story, or element chronologically or narratively comes before and influences or sets the stage for another within a mythic tradition.
-
D.
predecessorCompanion
Indicates that one entity previously served as a companion or partner to another entity before the current or referenced companion.
-
E.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f027a3d081908fc1134b50db3d45 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.