Triple
T3629682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poppaea Sabina |
E76923
|
entity |
| Predicate | marriedToEmperorIn |
P46634
|
FINISHED |
| Object | AD 62 |
—
|
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: AD 62 | Statement: [Poppaea Sabina, marriedToEmperorIn, AD 62]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToEmperorIn Context triple: [Poppaea Sabina, marriedToEmperorIn, AD 62]
-
A.
marriedToEmperor
chosen
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.
marriedToFutureMonarch
Indicates that one person is married to another person who will become a monarch in the future.
-
D.
reignAsEmpressConsortBegan
Indicates the point in time when an individual began their tenure or role as an empress consort.
-
E.
monarchSpouseReignStart
Indicates the date when a monarch’s spouse began their role as consort during the monarch’s reign.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc300223881909019982ebf194f78 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.