Triple
T35319129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeus Lepsynos |
E1019987
|
entity |
| Predicate | hasWorshipContext |
P53019
|
FINISHED |
| Object | city-state cult of Euromos |
—
|
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: city-state cult of Euromos | Statement: [Zeus Lepsynos, hasWorshipContext, city-state cult of Euromos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorshipContext Context triple: [Zeus Lepsynos, hasWorshipContext, city-state cult of Euromos]
-
A.
hasWorshipServices
Indicates that an entity conducts or provides organized religious worship services.
-
B.
hasLiturgicalContext
chosen
Indicates that something is associated with, used in, or relevant to a formal religious or liturgical setting or practice.
-
C.
hasWorshipSpaceFeature
Indicates that a worship space possesses or includes a particular feature, characteristic, or facility.
-
D.
hasLiveWorshipAtmosphere
Indicates that a place or event features an in-person, dynamic worship setting characterized by live participation and engagement.
-
E.
hasMinistryContext
Indicates that something is associated with, occurs within, or is defined in the context of a particular ministry or ministerial setting.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.