Triple
T8737707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutapa Kingdom |
E207425
|
entity |
| Predicate | religiousRoleOfRuler |
P84571
|
FINISHED |
| Object | spiritual intermediary |
—
|
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: spiritual intermediary | Statement: [Mutapa Kingdom, religiousRoleOfRuler, spiritual intermediary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousRoleOfRuler Context triple: [Mutapa Kingdom, religiousRoleOfRuler, spiritual intermediary]
-
A.
dynasticReligionRole
Indicates a relationship where an entity holds a religious office, function, or status specifically within the context of a ruling dynasty or hereditary line.
-
B.
religionOfMonarch
Indicates the religious affiliation or faith practiced by a given monarch.
-
C.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
-
D.
dynasticRole
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
E.
hasPrimaryReligionOfRulers
Indicates that the specified religion is the main or official faith practiced or endorsed by the rulers of an entity.
- 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_69ca835a03a081909d4d4cd01a18c9fb |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d45c96081909aa8509064ff3a04 |
completed | March 31, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc572d99bc819097f36b140c2ee1ce |
completed | March 31, 2026, 11:22 p.m. |
Created at: March 30, 2026, 6:38 p.m.