Triple
T2814622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arethusa |
E54251
|
entity |
| Predicate | escapeMethod |
P19454
|
FINISHED |
| Object | divine transformation |
—
|
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: divine transformation | Statement: [Arethusa, escapeMethod, divine transformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeMethod Context triple: [Arethusa, escapeMethod, divine transformation]
-
A.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
B.
methodOfDisappearance
chosen
Indicates the specific way or process by which an entity ceases to be present, visible, or existent.
-
C.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
D.
safetyFunction
Indicates that one entity serves as a safety-related function or mechanism that protects, safeguards, or reduces risk for another entity or process.
-
E.
helpedEscape
Indicates that one entity assisted another in getting away from confinement, danger, or pursuit.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4d29488190a32461906dd9ea7e |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.