Triple
T1761547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximian |
E38668
|
entity |
| Predicate | caesarAppointmentDate |
P15564
|
FINISHED |
| Object | 1 March 286 |
—
|
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: 1 March 286 | Statement: [Maximian, caesarAppointmentDate, 1 March 286]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caesarAppointmentDate Context triple: [Maximian, caesarAppointmentDate, 1 March 286]
-
A.
appointedOn
chosen
Indicates the specific date or time at which an entity is formally assigned or designated to a role, position, or responsibility.
-
B.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
C.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
D.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
-
E.
appointmentOnAdviceOf
Indicates that an appointment or selection of someone to a position is made based on the recommendation, counsel, or formal advice of another person or authority.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.