Triple
T2218360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | False Dmitry I |
E48082
|
entity |
| Predicate | succeededTitle |
P13335
|
FINISHED |
| Object | Tsar and Grand Prince of all Rus’ |
—
|
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: Tsar and Grand Prince of all Rus’ | Statement: [False Dmitry I, succeededTitle, Tsar and Grand Prince of all Rus’]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededTitle Context triple: [False Dmitry I, succeededTitle, Tsar and Grand Prince of all Rus’]
-
A.
receivedTitle
Indicates that an entity has been formally granted or awarded a specific title or honor.
-
B.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
C.
hadTitle
chosen
Indicates that an entity held or was assigned a specific title or formal designation.
-
D.
titleStatus
Indicates the current legal or administrative state of a title (such as ownership, validity, or processing stage) in relation to an entity or record.
-
E.
wonTitleWith
Indicates that an entity secured a specific title, award, or championship while being associated with or representing another entity (such as a team, organization, or group).
- 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.