Triple
T32547779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julian II |
E831890
|
entity |
| Predicate | wasCaesarOf |
P91642
|
FINISHED |
| Object | Gaul |
—
|
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: Gaul | Statement: [Julian II, wasCaesarOf, Gaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCaesarOf Context triple: [Julian II, wasCaesarOf, Gaul]
-
A.
governedAsCaesar
chosen
Indicates that an entity exercised ruling authority in the capacity or role of a Caesar (emperor).
-
B.
predecessorAsWesternAugustus
Indicates that one entity served as the immediately preceding holder of the title Western Augustus relative to another entity.
-
C.
predecessorAsCaesarOfTheEast
Indicates that one entity previously held the position of Caesar of the East immediately before the other entity in an official succession.
-
D.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
E.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5c12618819096751dd2e35f9f4f |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.