Triple
T30793399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aphrodite of Arles |
E784161
|
entity |
| Predicate | patronDeityDepicted |
P68508
|
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: [Aphrodite of Arles, patronDeityDepicted, Aphrodite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronDeityDepicted Context triple: [Aphrodite of Arles, patronDeityDepicted, Aphrodite]
-
A.
depictedDeity
Indicates that one entity is a deity who is shown or represented in an image, artwork, or visual depiction associated with another entity.
-
B.
patronDeityOf
Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
-
C.
depictedWithDeity
chosen
Indicates that an entity is shown or represented together with a particular deity in some form of depiction.
-
D.
portraysDeity
Indicates that one entity represents, depicts, or characterizes another entity as a deity or divine being.
-
E.
worshippedAs
Indicates that one entity is regarded and treated with religious reverence or devotion by 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6901035b88190ba857258707694cf |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:42 p.m.