Triple
T34589726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domitia Augusta |
E888144
|
entity |
| Predicate | imperialRole |
P121985
|
FINISHED |
| Object | consort of Domitian |
—
|
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: consort of Domitian | Statement: [Domitia Augusta, imperialRole, consort of Domitian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imperialRole Context triple: [Domitia Augusta, imperialRole, consort of Domitian]
-
A.
emperorRole
Indicates that an entity holds or fulfills the role, position, or office of an emperor in relation to another entity or context.
-
B.
imperialAddressee
Indicates that one entity is the person or group formally addressed by an imperial authority (e.g., emperor or empire) in a given communication or act.
-
C.
monarchicalRole
chosen
Indicates that one entity holds or is assigned a specific position, function, or office within a monarchical system of governance.
-
D.
monarchRole
Indicates that an entity holds or is assigned the role, office, or position of a monarch in relation to a state or domain.
-
E.
imperialRepresentation
Indicates that one entity serves as the official representative or embodiment of an empire or imperial authority in relation to another entity.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cb064c8190bd820ce3e44dc160 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.