Triple
T2814604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arethusa |
E54251
|
entity |
| Predicate | vowedTo |
P16811
|
FINISHED |
| Object | remain a virgin |
—
|
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: remain a virgin | Statement: [Arethusa, vowedTo, remain a virgin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vowedTo Context triple: [Arethusa, vowedTo, remain a virgin]
-
A.
hasOathTo
chosen
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
B.
primaryVows
Indicates that an entity has made or is bound by its main or foundational vows, promises, or commitments in a given context.
-
C.
tookReligiousVows
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
D.
swornInOn
Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
-
E.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
- 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.