Triple
T14788029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariamne |
E347578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish noblewoman |
C34500
|
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: Jewish noblewoman Context triple: [Mariamne, instanceOf, Jewish noblewoman]
-
A.
Polish noblewoman
A Polish noblewoman is a female member of the historical Polish szlachta, typically associated with landownership, social privilege, and participation in the political and cultural life of the Polish–Lithuanian Commonwealth.
-
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.
Prussian noblewoman
A Prussian noblewoman is an aristocratic woman from the historical Kingdom of Prussia, typically characterized by her high social rank, landowning family background, and adherence to the conservative, militaristic, and courtly traditions of Prussian society.
-
D.
Dutch noblewoman
A Dutch noblewoman is a female member of the Netherlands' aristocracy, typically holding a hereditary or granted title and associated with historical social status, landownership, and cultural influence.
-
E.
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.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.