Triple
T3409308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italica |
E71850
|
entity |
| Predicate | religionInRomanPeriod |
P49130
|
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: [Italica, religionInRomanPeriod, Roman polytheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionInRomanPeriod Context triple: [Italica, religionInRomanPeriod, Roman polytheism]
-
A.
religionInClassicalPeriod
Indicates that an entity’s religion or religious affiliation during the classical historical period is being specified.
-
B.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
C.
religionBeforeReformation
Indicates that an entity’s religious affiliation or practice existed or was established prior to the historical period known as the Reformation.
-
D.
dynasticReligion
Indicates that a dynasty or ruling family is associated with, practices, or is characterized by a particular religion.
-
E.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
- F. None of above. chosen
Provenance (4 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb90754788190ab85e2bec020f99e |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.