Triple
T10627494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmacis |
E250359
|
entity |
| Predicate | resultOfPrayer |
P95066
|
FINISHED |
| Object | fusion of bodies with Hermaphroditus |
—
|
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: fusion of bodies with Hermaphroditus | Statement: [Salmacis, resultOfPrayer, fusion of bodies with Hermaphroditus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfPrayer Context triple: [Salmacis, resultOfPrayer, fusion of bodies with Hermaphroditus]
-
A.
prayerIntention
Indicates that one entity directs a prayer or spiritual request specifically on behalf of, or concerning, another entity or situation.
-
B.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
C.
regardsPrayerAs
Indicates that one entity holds a particular attitude, evaluation, or characterization toward prayer as a practice or concept.
-
D.
canBePrayed
Indicates that an entity is a suitable or valid target for prayer or religious supplication.
-
E.
prayerForm
Indicates the specific manner, style, or structure in which a prayer is expressed or performed.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df8207f08190a6362a8ba00988b2 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 8:55 p.m.