Triple
T15763633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vassa of Novgorod |
E382161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Rus noble |
C32456
|
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: medieval Rus noble Context triple: [Vassa of Novgorod, instanceOf, medieval Rus noble]
-
A.
medieval European noble
chosen
A medieval European noble is a high-ranking member of the feudal aristocracy who holds land granted by a monarch in exchange for military service and governance over vassals and peasants.
-
B.
medieval Rus’ title
A medieval Rus’ title is a formal designation of rank, office, or nobility used in the political and social hierarchy of the East Slavic principalities from roughly the 9th to the 15th centuries.
-
C.
Finnish noble
A Finnish noble is a member of the historical aristocratic class in Finland, traditionally holding hereditary titles, land, and social privileges recognized by the Swedish and later Russian crowns, and organized through institutions such as the Finnish House of Nobility.
-
D.
nobleman
A nobleman is a male member of the aristocracy who holds a hereditary or granted title, social privileges, and often land or political influence within a hierarchical society.
-
E.
Mongol noble
A Mongol noble is a high-ranking member of Mongol society, typically belonging to ruling or aristocratic lineages, who holds political, military, and economic power within the Mongol Empire or its successor states.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:47 a.m.