Triple
T21793517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Polymius |
E538034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | figure in Christian tradition |
C26110
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: figure in Christian tradition Context triple: [King Polymius, instanceOf, figure in Christian tradition]
-
A.
place in Christian tradition
A place in Christian tradition is a spiritually or theologically significant location—earthly or heavenly—where key events of salvation history, worship, or divine presence are believed to occur or be especially manifest.
-
B.
figure in Christian mysticism
A figure in Christian mysticism is a person—historical, legendary, or symbolic—who embodies or mediates direct, experiential encounter with the divine, often through visions, contemplative practices, or ecstatic union with God.
-
C.
early Christian figure
An early Christian figure is an individual from the first centuries of Christianity who contributed to the formation, spread, or interpretation of the Christian faith through leadership, teaching, writing, or martyrdom.
-
D.
figure in Abrahamic religions
chosen
A figure in Abrahamic religions is an individual—divine, prophetic, angelic, or historical—who plays a significant role within the narratives, doctrines, or practices of Judaism, Christianity, and/or Islam.
-
E.
figure in Jewish tradition
A figure in Jewish tradition is an individual—historical, legendary, or symbolic—who plays a significant role in Jewish religious texts, narratives, law, or cultural memory.
- F. None of above.
Provenance (1 batch)
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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:52 p.m.