Triple
T874365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tolstoy family |
E18883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian noble family |
C811
|
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 noble family Context triple: [Tolstoy family, instanceOf, Russian noble family]
-
A.
noble family
chosen
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
-
B.
French aristocrat
A French aristocrat is a member of the historical French nobility, typically characterized by inherited titles, landownership, refined manners, and a prominent role in courtly and political life.
-
C.
French nobleman
A French nobleman is an aristocratic male from France who holds hereditary or granted titles, privileges, and social status within the traditional hierarchical nobility system.
-
D.
French noblewoman
A French noblewoman is an aristocratic woman from France who holds or inherits a noble title, typically associated with high social status, land ownership, and influence within the historical French social hierarchy.
-
E.
Dutch nobleman
A Dutch nobleman is a male member of the Netherlands' hereditary or titular nobility, historically holding social status, privileges, and often land or official positions within Dutch society.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.