Triple
T34209988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquilia Severa |
E877626
|
entity |
| Predicate | maritalStatusWithElagabalus |
P163910
|
FINISHED |
| Object | second wife |
—
|
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: second wife | Statement: [Aquilia Severa, maritalStatusWithElagabalus, second wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusWithElagabalus Context triple: [Aquilia Severa, maritalStatusWithElagabalus, second wife]
-
A.
maritalStatusInLegend
Indicates the marital status attributed to an entity within a legend, myth, or traditional narrative context.
-
B.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
C.
maritalStatusOfUnion
chosen
Indicates the type or state of the marital relationship that characterizes a particular union between entities.
-
D.
maritalStatusInDisguise
Indicates that an entity’s true marital status is being concealed or misrepresented, typically appearing different from what it actually is.
-
E.
hasCivilStatus
Indicates the civil or marital status that applies to a person or entity (e.g., single, married, divorced).
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:55 a.m.