Triple
T14754348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Yuri |
E346690
|
entity |
| Predicate | nobleFamily |
P914
|
FINISHED |
| Object | Yurievichi |
E69711
|
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: Yurievichi | Statement: [Prince Yuri, nobleFamily, Yurievichi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yurievichi Context triple: [Prince Yuri, nobleFamily, Yurievichi]
-
A.
Yurievichi
chosen
Yurievichi is a cadet branch of the medieval Rurikid ruling family that descended from Prince Yuri and governed various principalities in Kievan Rus’ and its successor states.
-
B.
Smolevichi
Smolevichi is a town in Belarus that serves as an administrative and economic center within the Minsk Region.
-
C.
Kalinkavichy
Kalinkavichy is a town in southeastern Belarus known as a local industrial and transport center within the Gomel Region.
-
D.
Zvenyhorodka
Zvenyhorodka is a town in central Ukraine that serves as a local administrative and cultural center within Cherkasy Oblast.
-
E.
Volochysk
Volochysk is a town in western Ukraine known as a local administrative and transportation center near the border with Ternopil Oblast.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d59df08190a86da5048358bd6e |
completed | April 14, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb9c725881908004368772fa528d |
completed | May 8, 2026, 3:05 p.m. |
Created at: April 10, 2026, 1:30 a.m.