Triple
T3828042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vibia Sabina |
E88739
|
entity |
| Predicate | marriedToEmperorFrom |
P37710
|
FINISHED |
| Object | 117 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: 117 CE | Statement: [Vibia Sabina, marriedToEmperorFrom, 117 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToEmperorFrom Context triple: [Vibia Sabina, marriedToEmperorFrom, 117 CE]
-
A.
marriedToEmperor
Indicates that one entity is the spouse of an emperor, signifying a marital relationship to a reigning or titled emperor.
-
B.
associatedWithEmperor
Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
-
C.
eraAsEmpress
chosen
Indicates the time period during which a person held the role or status of empress.
-
D.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
E.
marriedToFutureMonarch
Indicates that one person is married to another person who will become a monarch in the future.
- 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.