Triple
T776446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabratha |
E16395
|
entity |
| Predicate | religionHistorical |
P7641
|
FINISHED |
| Object | 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: polytheism | Statement: [Sabratha, religionHistorical, polytheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionHistorical Context triple: [Sabratha, religionHistorical, 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.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
C.
religionSignificant
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
-
D.
ethnicReligion
Indicates that a religion is closely associated with a particular ethnic group, often tied to that group’s culture, ancestry, or identity.
-
E.
foundedReligion
Indicates that an entity established or originated a particular religion.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.