Triple
T16216996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsesarevich |
E393617
|
entity |
| Predicate | relatedTitle |
P914
|
FINISHED |
| Object | Tsarevna |
E180589
|
NE 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: Tsarevna | Statement: [Tsesarevich, relatedTitle, Tsarevna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tsarevna Context triple: [Tsesarevich, relatedTitle, Tsarevna]
-
A.
Tsarevna of Russia
chosen
Tsarevna of Russia was the traditional title given to the daughters or daughters-in-law of a Russian tsar, denoting their status as imperial princesses within the Romanov dynasty.
-
B.
Pelageya
Pelageya is a Russian singer renowned for her powerful folk-inspired vocals and performances that blend traditional music with contemporary styles.
-
C.
Princess of Tver
Princess of Tver was a medieval Russian princely title held by female members of the ruling dynasty of the Principality of Tver.
-
D.
Rositsa
Rositsa is a river in northern Bulgaria that serves as a significant tributary of the Yantra River.
-
E.
Princess of Ryazan
Princess of Ryazan was a medieval Rus’ noble title held by the ruling princess consort of the Principality of Ryazan, a regional power in what is now central Russia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f660708190b6581ecfe218a15c |
completed | April 17, 2026, 12:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000796bc5c81909d2acb68851c9bb8 |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:03 a.m.