Triple
T2001792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petronius Maximus |
E43486
|
entity |
| Predicate | urbanPrefectOfRomeStart |
P35047
|
FINISHED |
| Object | c. 420s |
—
|
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: c. 420s | Statement: [Petronius Maximus, urbanPrefectOfRomeStart, c. 420s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPrefectOfRomeStart Context triple: [Petronius Maximus, urbanPrefectOfRomeStart, c. 420s]
-
A.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
B.
firstConsulshipYear
Indicates the calendar year in which an entity held its first consulship or began serving its first term as consul.
-
C.
reignAsAugustusOfTheWest
Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
-
D.
cityDuringImperialPeriod
Indicates that a location functioned as a city during a specified imperial or empire-dominated historical period.
-
E.
firstCaesarInWest
Indicates that the subject is recognized as the earliest or original holder of the title "Caesar" in the Western context.
- F. None of above. chosen
Provenance (4 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb880c710819098fb877052ce56dc |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb87b9fc08190a748c278ef2d7dc7 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:37 p.m.