Triple
T18166580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lufton |
E434910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional aristocratic 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: fictional aristocratic family Context triple: [Lufton, instanceOf, fictional aristocratic 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.
Renaissance family
A Renaissance family is a kinship group in early modern Europe whose structure, roles, and daily life were shaped by humanist ideals, emerging social mobility, and the cultural, economic, and religious transformations of the 14th–17th centuries.
-
C.
Georgian noble family
A Georgian noble family is a hereditary lineage from Georgia historically endowed with social prestige, land, and political influence within the country’s aristocratic hierarchy.
-
D.
British dynasty
A British dynasty is a succession of rulers or influential family members from the same lineage who hold power or prominence in Britain over multiple generations.
-
E.
fictional monarchy
A fictional monarchy is an imagined system of government in which a royal family or single sovereign rules a realm, often shaped by invented histories, cultures, and political dynamics.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:30 a.m.