Triple
T18346086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mowbray family |
E439542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval aristocratic house |
C35075
|
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 aristocratic house Context triple: [Mowbray family, instanceOf, medieval aristocratic house]
-
A.
medieval mansion
A medieval mansion is a large, fortified residence of nobility featuring stone construction, great halls, defensive elements, and expansive grounds reflecting wealth and social status in the Middle Ages.
-
B.
aristocratic mansion
An aristocratic mansion is a grand, opulent residence historically owned by nobility or the elite, characterized by expansive grounds, elaborate architecture, and richly decorated interiors that symbolize wealth, power, and social status.
-
C.
Vassal house
chosen
A vassal house is a noble family sworn to serve, support, and owe allegiance—often through military and political obligations—to a more powerful ruling house or liege.
-
D.
medieval nobility
Medieval nobility comprised the hereditary warrior-elite who held land from a monarch in exchange for military and political service, dominating social, economic, and legal life in feudal Europe.
-
E.
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.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:37 a.m.