Triple
T5682495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhea Silvia |
E125229
|
entity |
| Predicate | violatedVestalVowBy |
P2111
|
FINISHED |
| Object | conceiving Romulus and Remus |
—
|
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: conceiving Romulus and Remus | Statement: [Rhea Silvia, violatedVestalVowBy, conceiving Romulus and Remus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violatedVestalVowBy Context triple: [Rhea Silvia, violatedVestalVowBy, conceiving Romulus and Remus]
-
A.
violationOf
Indicates that one entity breaches, disobeys, or infringes upon a rule, law, agreement, or right associated with another entity.
-
B.
penaltyForBreakingOath
Indicates the punishment or negative consequence imposed when an oath is violated.
-
C.
vowedVirtue
Indicates that an entity has formally promised or committed to uphold a particular virtue or moral quality.
-
D.
violatedPrinciple
chosen
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
E.
wasCheatedOnBy
Indicates that one entity was the victim of infidelity committed by another entity in a romantic or committed relationship.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.