Triple
T2018908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capua |
E44058
|
entity |
| Predicate | religionInHistory |
P7641
|
FINISHED |
| Object | Roman paganism |
—
|
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 paganism | Statement: [Capua, religionInHistory, Roman paganism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionInHistory Context triple: [Capua, religionInHistory, Roman paganism]
-
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.
historicalDoctrine
Indicates that one entity embodies, represents, or is associated with a doctrine, teaching, or set of principles originating from a past historical context.
-
D.
religionInClassicalPeriod
Indicates that an entity’s religion or religious affiliation during the classical historical period is being specified.
-
E.
religionSignificant
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8cfa5c88190b55bce5db968665b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.