Triple
T18552563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyldenstierne family |
E453413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norwegian noble family |
C19839
|
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: Norwegian noble family Context triple: [Gyldenstierne family, instanceOf, Norwegian noble family]
-
A.
Swedish noble family
A Swedish noble family is a lineage of individuals in Sweden historically granted hereditary noble status, often holding titles, estates, and social privileges recognized by the Swedish nobility system.
-
B.
Norwegian noble
chosen
A Norwegian noble is a member of the historical aristocratic class in Norway, traditionally holding hereditary titles, land, and social privileges within the Norwegian realm.
-
C.
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.
-
D.
Swedish noble
A Swedish noble is a member of Sweden’s historically privileged aristocratic estate, traditionally holding hereditary titles, social status, and often land or political influence within the Swedish realm.
-
E.
Prussian aristocratic family
A Prussian aristocratic family is a noble lineage rooted in the historical Kingdom of Prussia, characterized by hereditary titles, landed estates, military and bureaucratic service, and adherence to traditional social hierarchies and customs.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:38 a.m.