Triple
T32797688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushite pantheon |
E838810
|
entity |
| Predicate | hasRoyalPatronDeity |
P51997
|
FINISHED |
| Object | Amun of Napata |
—
|
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: Amun of Napata | Statement: [Kushite pantheon, hasRoyalPatronDeity, Amun of Napata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalPatronDeity Context triple: [Kushite pantheon, hasRoyalPatronDeity, Amun of Napata]
-
A.
patronDeityOf
chosen
Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
-
B.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
C.
hasRoyalPatronageSince
Indicates that an entity has been under the official support or sponsorship of a royal person or institution starting from a specified point in time.
-
D.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
-
E.
hasSignificanceForDeity
Indicates that something holds particular importance, value, or meaning in relation to a specific deity.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 1, 2026, 1:14 a.m.