Triple
T14787029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry the Bearded |
E347553
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 13th-century Polish politician |
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: 13th-century Polish politician Context triple: [Henry the Bearded, instanceOf, 13th-century Polish politician]
-
A.
Polish–Lithuanian nobleman
A Polish–Lithuanian nobleman was a member of the szlachta elite of the Polish–Lithuanian Commonwealth, holding hereditary privileges, political rights, and often landed estates within its multiethnic realm.
-
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.
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.
-
E.
13th-century English politician
A 13th-century English politician was a medieval figure involved in the governance of England, often serving in roles such as a member of Parliament, royal administrator, or local official under the monarchy.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.