Triple
T1744815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius Nepos |
E38312
|
entity |
| Predicate | continuedToClaimTitle |
P5052
|
FINISHED |
| Object | Emperor of the Western Roman Empire |
—
|
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: Emperor of the Western Roman Empire | Statement: [Julius Nepos, continuedToClaimTitle, Emperor of the Western Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedToClaimTitle Context triple: [Julius Nepos, continuedToClaimTitle, Emperor of the Western Roman Empire]
-
A.
claimedTitle
chosen
Indicates that an entity asserts or declares possession of a particular title or rank.
-
B.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
C.
regainedTitleFrom
Indicates that an entity has recovered a previously held title or position from another entity who had taken or held it in the interim.
-
D.
titleContested
Indicates that the legitimacy or ownership of a title is disputed between parties.
-
E.
reignClaimStart
Indicates the point in time when a person’s asserted or contested rule or reign is claimed to have begun.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab630e7d008190a8c673665d9672bb |
completed | March 6, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69aa61c5a18481909bc49e0c54d64314 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.