Triple
T8915296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liternum |
E212280
|
entity |
| Predicate | hasReligionHistoricallyPracticed |
P7641
|
FINISHED |
| Object | Roman 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: Roman polytheism | Statement: [Liternum, hasReligionHistoricallyPracticed, Roman polytheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionHistoricallyPracticed Context triple: [Liternum, hasReligionHistoricallyPracticed, Roman polytheism]
-
A.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
B.
hasFormerReligiousJurisdiction
Indicates that an entity was previously under the religious authority or governance of another entity, but no longer is.
-
C.
usedReligionFor
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
D.
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.
-
E.
hasContinuousReligiousFunctionSince
Indicates that a religious function or use has been ongoing without interruption from a specified starting time up to the present or another reference time.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc660f6a088190b0af829ea809d8ad |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.