Triple
T32706904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civitas Lanuvinorum |
E836297
|
entity |
| Predicate | hasNotableCult |
P203240
|
FINISHED |
| Object | cult of Juno Sospita |
—
|
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: cult of Juno Sospita | Statement: [Civitas Lanuvinorum, hasNotableCult, cult of Juno Sospita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCult Context triple: [Civitas Lanuvinorum, hasNotableCult, cult of Juno Sospita]
-
A.
hasCultFollowing
Indicates that something has attracted a small but highly dedicated and enthusiastic group of supporters or fans.
-
B.
notableCultTitle
Indicates that an entity holds a title or designation that is especially prominent or significant within a particular cult or cult-like group.
-
C.
hasCultSince
Indicates that an entity has had an organized group of devoted followers (a cult) continuously since a specified time or date.
-
D.
hasCultFeature
Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
-
E.
notableSubculture
Indicates that one entity is a significant or well-recognized subculture within the context or domain of the other entity.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a01416f8a8c8190abc12f68bd23dcc3 |
completed | May 11, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_6a013f3bc2e48190a51ec2707bbdd474 |
completed | May 11, 2026, 2:30 a.m. |
| PDg | Predicate description generation | batch_6a01416eb9588190ad74541d0640a4ba |
completed | May 11, 2026, 2:39 a.m. |
Created at: May 1, 2026, 1:10 a.m.