Triple
T34210006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquilia Severa |
E877626
|
entity |
| Predicate | statusBeforeMarriage |
P199646
|
FINISHED |
| Object | consecrated Vestal 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: consecrated Vestal Virgin | Statement: [Aquilia Severa, statusBeforeMarriage, consecrated Vestal Virgin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBeforeMarriage Context triple: [Aquilia Severa, statusBeforeMarriage, consecrated Vestal Virgin]
-
A.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
B.
marriageBefore
Indicates that one marriage event occurred earlier in time than another marriage event.
-
C.
socialStatusBeforeSecondMarriage
Indicates the social status an individual held prior to entering into their second marriage.
-
D.
socialStatusAfterMarriage
Indicates the social status an individual holds as a result of, or following, their marriage.
-
E.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
| PDg | Predicate description generation | batch_69ff49f7db2c819094d488d13985334c |
completed | May 9, 2026, 2:51 p.m. |
Created at: May 1, 2026, 1:55 a.m.