Triple
T14646649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psyche |
E343867
|
entity |
| Predicate | relationshipWithAphrodite |
P115204
|
FINISHED |
| Object | rival in beauty |
—
|
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: rival in beauty | Statement: [Psyche, relationshipWithAphrodite, rival in beauty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithAphrodite Context triple: [Psyche, relationshipWithAphrodite, rival in beauty]
-
A.
AphroditeBribe
Indicates that one entity (Aphrodite) offers or gives a persuasive incentive or reward to another entity in order to influence their decision or allegiance.
-
B.
associatedGoddess
Indicates that one entity is recognized as the goddess traditionally linked or connected to another entity (such as a place, concept, or deity).
-
C.
hasLoveAndFertilityGoddess
Indicates that an entity is associated with or possesses a goddess who embodies both love and fertility.
-
D.
relationshipToHermaphroditus
Indicates the specific familial, romantic, or social relationship that one entity has to Hermaphroditus.
-
E.
poseidonRelation
Indicates a mythological or symbolic relationship involving Poseidon, such as kinship, patronage, or influence over another 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ebe8048190a2935d00c9cfd8be |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.