Triple
T11997060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Montague |
E285558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional 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: fictional noble family Context triple: [House of Montague, instanceOf, fictional 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.
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.
-
C.
fictional household
A fictional household is an imagined domestic setting, including its members, relationships, routines, and environment, created within a narrative to explore themes, conflicts, and everyday life.
-
D.
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.
-
E.
literary family
A literary family is a group of related writers or a fictional family whose interconnected lives, works, and narratives collectively explore themes, histories, and identities across generations.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:46 p.m.