Triple
T30050651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortuna Primigenia cult |
E763591
|
entity |
| Predicate | ritualSpaceType |
P27744
|
FINISHED |
| Object | terraced sanctuary |
—
|
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: terraced sanctuary | Statement: [Fortuna Primigenia cult, ritualSpaceType, terraced sanctuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualSpaceType Context triple: [Fortuna Primigenia cult, ritualSpaceType, terraced sanctuary]
-
A.
ritualStructure
Indicates a relationship where an entity is a structure or built feature specifically used for performing rituals or ceremonial practices.
-
B.
hasRitualSpace
chosen
Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
-
C.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
D.
ritualsDirectedAt
Indicates that certain rituals are performed with a specific entity, object, or target as their intended focus or recipient.
-
E.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67a1567c0819095851e4b9a9c322b |
completed | May 2, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:55 p.m.