Triple
T18928896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Gorizia |
E463046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval European noble family |
C27403
|
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 European noble family Context triple: [House of Gorizia, instanceOf, medieval European noble family]
-
A.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
-
B.
medieval ruling family
A medieval ruling family is a hereditary dynasty that holds political power, land, and social authority over a realm, often legitimized by lineage, religion, and military strength.
-
C.
medieval Roman noble family
A medieval Roman noble family is an aristocratic lineage based in Rome during the Middle Ages, wielding political, economic, and social influence through landholdings, alliances, and roles in civic and ecclesiastical institutions.
-
D.
medieval French dynasty
A medieval French dynasty is a ruling family that held hereditary power over French territories during the Middle Ages, shaping the kingdom’s political, social, and cultural development through successive generations of monarchs.
-
E.
Hungarian noble family
chosen
A Hungarian noble family is a historically recognized lineage within the Kingdom of Hungary’s aristocracy, holding hereditary titles, lands, and social privileges passed down through 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:59 a.m.