Triple
T21793528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Polymius |
E538034
|
entity |
| Predicate | preConversionReligion |
P111
|
FINISHED |
| Object | pagan |
—
|
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: pagan | Statement: [King Polymius, preConversionReligion, pagan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preConversionReligion Context triple: [King Polymius, preConversionReligion, pagan]
-
A.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
B.
laterRevertedReligion
Indicates that an entity adopted a religion and then subsequently reverted or returned to a previous or different religious affiliation.
-
C.
religiousConversionPeriod
Indicates the time span during which an entity undergoes or is involved in a process of religious conversion.
-
D.
religionBeforeReformation
Indicates that an entity’s religious affiliation or practice existed or was established prior to the historical period known as the Reformation.
-
E.
formerReligiousAffiliation
chosen
Indicates that an entity previously adhered to a particular religion or religious denomination but no longer does so.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f06221d1f4819089bb113d808d79c2 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.