Triple
T35484399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George II of Brzeg |
E1025552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 16th-century Polish prince |
C13805
|
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: 16th-century Polish prince Context triple: [George II of Brzeg, instanceOf, 16th-century Polish prince]
-
A.
Polish prince
A Polish prince is a male member of the historical Polish nobility or royal family, often holding hereditary titles, lands, and political influence within the Polish–Lithuanian Commonwealth or its predecessor states.
-
B.
Polish duke
chosen
A Polish duke is a high-ranking nobleman in Poland, historically holding significant territorial authority, political influence, and social prestige within the Polish–Lithuanian Commonwealth or earlier Piast and Jagiellonian realms.
-
C.
Polish legendary ruler
A Polish legendary ruler is a mythic or semi-mythic sovereign from Poland’s early tradition, known primarily through folklore, chronicles, and national legends rather than verified historical records.
-
D.
Duke of Sandomierz
The Duke of Sandomierz was a medieval Polish noble title denoting the ruler of the Sandomierz region, often held by members of the Piast dynasty as part of the fragmented Polish kingdom.
-
E.
King of Poland
The King of Poland was the sovereign ruler of the Polish state, historically elected by the nobility and responsible for governing the kingdom, leading its armies, and representing it in foreign affairs.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.