Triple
T25695778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palaepaphos |
E644316
|
entity |
| Predicate | isCultCenterOf |
P114792
|
FINISHED |
| Object | Aphrodite |
—
|
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: Aphrodite | Statement: [Palaepaphos, isCultCenterOf, Aphrodite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCultCenterOf Context triple: [Palaepaphos, isCultCenterOf, Aphrodite]
-
A.
centerOfCultFrom
chosen
Indicates that a location serves as the primary cult center or focal place of worship originating from a particular source or entity.
-
B.
centerOfCult
Indicates that the subject functions as the primary focus or core figure around which a cult is organized or devoted.
-
C.
associatedWithCultCenter
Indicates a relationship where something (such as a deity, object, or practice) is linked to, connected with, or primarily related to a specific cult center or place of worship.
-
D.
hasCultPlaceType
Indicates that an entity is associated with a place used for cultic or religious activities of a specified type.
-
E.
isCulturalCenterFor
Indicates that one entity serves as a primary hub or focal point for the cultural activities, heritage, or identity of another entity.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fbc4327c819090506ac08479faca |
completed | May 2, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 8:35 p.m.