Triple
T1262053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard III of England |
E12521
|
entity |
| Predicate | reintermentDate |
P21038
|
FINISHED |
| Object | 2015-03-26 |
—
|
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: 2015-03-26 | Statement: [Richard III of England, reintermentDate, 2015-03-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reintermentDate Context triple: [Richard III of England, reintermentDate, 2015-03-26]
-
A.
reburialDate
chosen
Indicates the date on which something that was previously buried is buried again.
-
B.
dateOfBurial
Indicates the specific date on which an entity was buried.
-
C.
firstBurial
Indicates that an entity is the earliest or initial burial associated with a person, place, or burial context.
-
D.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
E.
rededicationDate
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc77f4c8190b97a0ceaa31cfd49 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.