Triple
T32541442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cult of Jupiter Latiaris |
E831722
|
entity |
| Predicate | majorRite |
P11123
|
FINISHED |
| Object | Feriae Latinae |
—
|
NE NERFINISHED |
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: Feriae Latinae | Statement: [cult of Jupiter Latiaris, majorRite, Feriae Latinae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRite Context triple: [cult of Jupiter Latiaris, majorRite, Feriae Latinae]
-
A.
majorLiturgy
Indicates a relationship where a liturgical text, rite, or ceremony is classified as a primary or principal form of worship within a religious tradition.
-
B.
dominantRite
Indicates that one religious rite or liturgical tradition holds primary or prevailing status over others within a given context or community.
-
C.
ordinationRite
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
-
D.
majorSchism
Indicates a significant and formal split or division between previously unified groups, organizations, or factions.
-
E.
notableRite
chosen
Indicates that an entity is associated with a significant or distinguished ritual, ceremony, or formal rite.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1:02 a.m.