Triple
T1184836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nubia |
E25220
|
entity |
| Predicate | hasReligionHistorical |
P7641
|
FINISHED |
| Object | ancient Nubian polytheism |
—
|
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: ancient Nubian polytheism | Statement: [Nubia, hasReligionHistorical, ancient Nubian polytheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionHistorical Context triple: [Nubia, hasReligionHistorical, ancient Nubian polytheism]
-
A.
religionHistoricallyAssociated
chosen
Indicates a historical association between an entity and a particular religion, based on past practice, tradition, or cultural linkage rather than current or official status.
-
B.
dominantReligionLegacy
Indicates that a historically dominant religion has left a lasting influence or heritage on a society, culture, or region.
-
C.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
D.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
E.
hasReligiousOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd39245881908766c41943dc2752 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.