Triple
T30530996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Tetrarchy |
E776998
|
entity |
| Predicate | hasCaesar |
P195860
|
FINISHED |
| Object | Severus II |
—
|
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: Severus II | Statement: [Second Tetrarchy, hasCaesar, Severus II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaesar Context triple: [Second Tetrarchy, hasCaesar, Severus II]
-
A.
coCaesarWith
Indicates that two individuals simultaneously held the title or role of Caesar together, sharing imperial authority during the same period.
-
B.
hasAugustus
Indicates that one entity possesses, is associated with, or is characterized by an Augustus (such as a person named Augustus, a title, or an object so designated).
-
C.
hasCAS
Indicates that an entity is associated with a specific Chemical Abstracts Service (CAS) registry number identifying it as a distinct chemical substance.
-
D.
dateOfCaesarAppointment
Indicates the date on which an individual was appointed to the position or title of Caesar.
-
E.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
- F. None of above. chosen
Provenance (4 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_69fdec5f0420819087c0230ad384c4ba |
completed | May 8, 2026, 1:59 p.m. |
Created at: April 29, 2026, 8:18 p.m.