Triple
T13365237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Calpurnius Piso Licinianus |
E318921
|
entity |
| Predicate | dateOfHeirDesignation |
P6938
|
FINISHED |
| Object | 10 January 69 |
—
|
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: 10 January 69 | Statement: [Lucius Calpurnius Piso Licinianus, dateOfHeirDesignation, 10 January 69]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfHeirDesignation Context triple: [Lucius Calpurnius Piso Licinianus, dateOfHeirDesignation, 10 January 69]
-
A.
royalDesignationYear
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
B.
appointedCrownPrinceDate
Indicates the date on which an individual was formally appointed to the position of crown prince.
-
C.
dateOfSuccession
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
-
D.
dateProclaimed
Indicates the specific date on which something was formally declared, announced, or proclaimed.
-
E.
designationDate
chosen
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da628c71ac81908cfa36342077766e |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.