Triple
T30725790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Nikolaus Esterházy |
E782276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Esterházy family |
C7273
|
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: member of the Esterházy family Context triple: [Prince Nikolaus Esterházy, instanceOf, member of the Esterházy family]
-
A.
member of the Schwarzenberg family
A member of the Schwarzenberg family is an individual belonging by birth or legal affiliation to the historically significant European noble house of Schwarzenberg, associated with political influence, military leadership, and extensive landholdings.
-
B.
member of the House of Este
A member of the House of Este is an individual belonging to the historic Italian noble dynasty that ruled territories such as Ferrara, Modena, and Reggio and played a significant role in European politics and culture from the Middle Ages onward.
-
C.
member of the Sobieski family
A member of the Sobieski family is an individual belonging by birth or legal relation to the historically significant Polish noble and royal lineage associated with the Sobieski name.
-
D.
member of the Árpád dynasty
A member of the Árpád dynasty is an individual belonging to the medieval Hungarian royal house that ruled the Kingdom of Hungary and its predecessor entities from the late 9th century until 1301.
-
E.
Austrian noble
chosen
An Austrian noble is a member of the historical aristocracy of Austria, typically holding hereditary titles, land, and social privileges within the Habsburg and later Austrian realms.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:36 p.m.