Triple
T32055538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio II Italica |
E818607
|
entity |
| Predicate | laterEmperorAssociated |
P27872
|
FINISHED |
| Object | Diocletian |
—
|
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: Diocletian | Statement: [Legio II Italica, laterEmperorAssociated, Diocletian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEmperorAssociated Context triple: [Legio II Italica, laterEmperorAssociated, Diocletian]
-
A.
associatedWithEmperor
chosen
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.
-
B.
laterSupportedEmperor
Indicates that an entity provided support to an emperor at a later time or stage, rather than during the emperor’s initial rise or earlier period.
-
C.
eraOfEmperor
Indicates the historical time period during which a particular emperor held power or reigned.
-
D.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
E.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: May 1, 2026, 12:21 a.m.