Triple
T30681236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Cassianius Latinius Postumus |
E781056
|
entity |
| Predicate | declaredEmperorInYear |
P84111
|
FINISHED |
| Object | 260 |
—
|
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: 260 | Statement: [Marcus Cassianius Latinius Postumus, declaredEmperorInYear, 260]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredEmperorInYear Context triple: [Marcus Cassianius Latinius Postumus, declaredEmperorInYear, 260]
-
A.
declaredHimselfEmperorInYear
chosen
Indicates that a person formally proclaimed himself to be emperor in a specific year.
-
B.
declaredHimselfEmperorIn
Indicates that a person formally proclaimed himself emperor in a specific place or at a specific time.
-
C.
proclaimedEmperorBy
Indicates that one entity formally declares or recognizes another entity as emperor.
-
D.
proclaimedEmperorIn
Indicates that an individual was formally declared or recognized as emperor in a specific place or at a specific time.
-
E.
coronationAsCoEmperorDate
Indicates the date on which an individual was formally crowned or installed as a co-emperor alongside another reigning 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:32 p.m.