Triple
T14472383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Basarab |
E358876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Romanian noble house |
C34824
|
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: Romanian noble house Context triple: [House of Basarab, instanceOf, Romanian noble house]
-
A.
Hungarian noble family
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.
-
B.
Polish-Lithuanian noble family
A Polish-Lithuanian noble family is a lineage belonging to the historical szlachta estate of the Polish-Lithuanian Commonwealth, characterized by hereditary titles, coats of arms, landholdings, and participation in the region’s political and social life.
-
C.
Alsatian noble house
An Alsatian noble house is an aristocratic family originating from the Alsace region, historically holding hereditary titles, lands, and political influence within the shifting sovereignties of France and the Holy Roman Empire.
-
D.
Romanian noblewoman
A Romanian noblewoman is a high-born woman from Romania’s historical aristocracy, often associated with landownership, political influence, and the preservation of regional cultural traditions.
-
E.
Hungarian noble
A Hungarian noble is a member of the historical aristocratic class of the Kingdom of Hungary, holding hereditary titles, land, and political privileges within the kingdom’s feudal and later constitutional systems.
- F. None of above. chosen
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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.