Triple
T32797686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushite pantheon |
E838810
|
entity |
| Predicate | hasPrimaryWarDeity |
P126679
|
FINISHED |
| Object | Apedemak |
—
|
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: Apedemak | Statement: [Kushite pantheon, hasPrimaryWarDeity, Apedemak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryWarDeity Context triple: [Kushite pantheon, hasPrimaryWarDeity, Apedemak]
-
A.
hasWarDeity
chosen
Indicates that an entity has a specific deity associated with war as part of its religious or mythological system.
-
B.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
C.
hasGuardianDeity
Indicates that an entity is under the protection or patronage of a specific guardian deity.
-
D.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
E.
hasSecondaryDeity
Indicates that an entity has an associated secondary or subordinate deity linked to it.
- 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_6a011ee3507081908b42de4278ae0b83 |
completed | May 11, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_6a011e874420819091cac3f08e8aa3f9 |
completed | May 11, 2026, 12:10 a.m. |
Created at: May 1, 2026, 1:14 a.m.