Triple
T21286584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Milica of Montenegro |
E524675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian courtier |
C6316
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Russian courtier Context triple: [Princess Milica of Montenegro, instanceOf, Russian courtier]
-
A.
Russian prince
A Russian prince is a male noble of princely rank in Russia, historically belonging to the aristocratic ruling class and often holding political, military, or territorial authority within the Russian Empire or its predecessor states.
-
B.
Russian noblewoman
chosen
A Russian noblewoman is an aristocratic woman of the Russian Empire or nobility, typically distinguished by her high social rank, landowning family background, and participation in elite cultural and political life.
-
C.
Russian grand duchess
A Russian grand duchess is a female member of the Russian imperial family, typically the daughter or granddaughter of a tsar, holding high noble rank and associated with significant social and political status in the Russian Empire.
-
D.
Russian provincial teacher
A Russian provincial teacher is an underpaid, overworked educator in a small town or rural area who struggles with outdated resources, bureaucratic pressure, and social marginalization while trying to provide meaningful instruction to local children.
-
E.
Russian diplomat
A Russian diplomat is an official representative of the Russian Federation who conducts negotiations, manages international relations, and protects Russia’s interests and citizens abroad through diplomatic channels.
- F. None of above.
Provenance (1 batch)
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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:03 p.m.