Triple
T3828043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vibia Sabina |
E88739
|
entity |
| Predicate | marriedToEmperorUntil |
P37710
|
FINISHED |
| Object | 136 CE |
—
|
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: 136 CE | Statement: [Vibia Sabina, marriedToEmperorUntil, 136 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToEmperorUntil Context triple: [Vibia Sabina, marriedToEmperorUntil, 136 CE]
-
A.
marriedToEmperor
Indicates that one entity is the spouse of an emperor, signifying a marital relationship to a reigning or titled emperor.
-
B.
eraAsEmpress
chosen
Indicates the time period during which a person held the role or status of empress.
-
C.
reignAsEmpressConsortBegan
Indicates the point in time when an individual began their tenure or role as an empress consort.
-
D.
monarchSpouseReignStart
Indicates the date when a monarch’s spouse began their role as consort during the monarch’s reign.
-
E.
spouseIsLastIndependentRulerOf
Indicates that the subject’s spouse is recognized as the final ruler of a polity who governed independently, before loss of sovereignty or incorporation into another 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8459f881908a2c91bb07e381ef |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.