Triple
T31759118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthias I |
E810632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Hunyadi family |
C61236
|
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 Hunyadi family Context triple: [Matthias I, instanceOf, member of the Hunyadi family]
-
A.
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.
-
B.
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.
-
C.
member of Brâncoveanu family
A member of the Brâncoveanu family is an individual belonging by blood or marriage to the historic Romanian noble lineage associated with Prince Constantin Brâncoveanu and his descendants.
-
D.
member of the Billung dynasty
A member of the Billung dynasty is an individual belonging to the medieval German noble family that held significant ducal power in Saxony from the 10th to early 12th centuries.
-
E.
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.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:30 p.m.