Triple
T25112404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count László Széchenyi |
E629031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian aristocrat |
C33038
|
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: Hungarian aristocrat Context triple: [Count László Széchenyi, instanceOf, Hungarian aristocrat]
-
A.
Hungarian noble
chosen
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.
-
B.
Hungarian noblewoman
A Hungarian noblewoman is a female member of Hungary’s historical aristocracy, typically distinguished by inherited titles, landownership, and a prominent role in social, cultural, and sometimes political life.
-
C.
Austrian noble
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.
-
D.
Belgian aristocrat
A Belgian aristocrat is a member of Belgium’s hereditary nobility, typically bearing a noble title, upholding longstanding family traditions, and often participating in the country’s cultural, social, and sometimes political life.
-
E.
Bohemian nobleman
A Bohemian nobleman is an aristocrat from the historical Kingdom of Bohemia, distinguished by hereditary titles, landownership, and a role in the region’s political and cultural life.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:27 a.m.