Triple
T10914812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronation of Queen Victoria |
E257790
|
entity |
| Predicate | accessionDateOfMonarch |
P47970
|
FINISHED |
| Object | 20 June 1837 |
—
|
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: 20 June 1837 | Statement: [Coronation of Queen Victoria, accessionDateOfMonarch, 20 June 1837]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessionDateOfMonarch Context triple: [Coronation of Queen Victoria, accessionDateOfMonarch, 20 June 1837]
-
A.
currentMonarchBirthDate
Indicates the date on which the person who is the current monarch of a specified realm was born.
-
B.
monarchAtTime
Indicates that a specified person holds the position of monarch of a given polity during a particular time or time interval.
-
C.
reignOfMonarch
Indicates the period during which a specific monarch holds ruling authority over a realm or territory.
-
D.
dateOfSuccession
chosen
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
-
E.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77073d12881908ea59771b84bc804 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d70d3f9dc88190a686a8b0dd6a3b21 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.