Triple
T30874282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinian |
E786431
|
entity |
| Predicate | predecessorAsCoEmperor |
P133469
|
FINISHED |
| Object | Licinius 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: Licinius II | Statement: [Martinian, predecessorAsCoEmperor, Licinius II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsCoEmperor Context triple: [Martinian, predecessorAsCoEmperor, Licinius II]
-
A.
predecessorAsCoRuler
chosen
Indicates that one entity previously shared ruling authority with another entity before being succeeded in that co-ruler position.
-
B.
predecessorAsMotherOfEmperor
Indicates that one entity is the mother of an emperor and is the immediate predecessor in that maternal role to another such mother.
-
C.
predecessorAsEasternRuler
Indicates that one entity previously held the position of eastern ruler before another entity assumed that same role.
-
D.
predecessorAsLatinEmperor
Indicates that one entity previously held the position of Latin Emperor immediately before the other entity.
-
E.
successorAsCoEmperor
Indicates that one entity becomes the next co-emperor following another entity in a shared imperial rule.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 8:48 p.m.