Triple
T25460044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornelia Salonina |
E638019
|
entity |
| Predicate | marriedToEmperorDuringReign |
P46634
|
FINISHED |
| Object | Gallienus |
—
|
NE NERFINISHED |
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: Gallienus | Statement: [Cornelia Salonina, marriedToEmperorDuringReign, Gallienus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToEmperorDuringReign Context triple: [Cornelia Salonina, marriedToEmperorDuringReign, Gallienus]
-
A.
marriedToEmperor
chosen
Indicates that one entity is the spouse of an emperor, signifying a marital relationship to a reigning or titled emperor.
-
B.
marriedToMonarchUntil
Indicates that an individual was married to a monarch up to a specified end point in time, after which the marriage no longer held.
-
C.
spouseReignName
Indicates the official reign name or title held by a person's spouse during their period of rule.
-
D.
marriedToMonarchFrom
Indicates that a person is married to a monarch who rules or comes from a specified country or region.
-
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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 2:11 p.m.