Triple
T9463302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faustina the Elder |
E228202
|
entity |
| Predicate | spouseBecameEmperor |
P15466
|
FINISHED |
| Object | 138 |
—
|
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: 138 | Statement: [Faustina the Elder, spouseBecameEmperor, 138]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseBecameEmperor Context triple: [Faustina the Elder, spouseBecameEmperor, 138]
-
A.
marriedToEmperor
Indicates that one entity is the spouse of an emperor, signifying a marital relationship to a reigning or titled emperor.
-
B.
reignAsEmpressConsortBegan
chosen
Indicates the point in time when an individual began their tenure or role as an empress consort.
-
C.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
D.
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.
-
E.
spouseIsMonarchOf
Indicates that a person's spouse holds the position of monarch (ruler) of a specified country or territory.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcd9794819093c392489d4efbe9 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.