Triple
T2218351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | False Dmitry I |
E48082
|
entity |
| Predicate | coronationYear |
P14035
|
FINISHED |
| Object | 1605 |
—
|
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: 1605 | Statement: [False Dmitry I, coronationYear, 1605]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationYear Context triple: [False Dmitry I, coronationYear, 1605]
-
A.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
B.
coronationPeriod
Indicates the time span during which a coronation event takes place or is in effect.
-
C.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
D.
royalDesignationYear
chosen
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
E.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc011d50c8190b1c375cc633f8189 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.