Triple
T12740927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May 3rd Constitution |
E304486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish historical document |
C31822
|
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: Polish historical document Context triple: [May 3rd Constitution, instanceOf, Polish historical document]
-
A.
Polish military history event
A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
-
B.
institution of the Polish government-in-exile
An institution of the Polish government-in-exile is an official body established by the displaced Polish state during and after World War II to represent Poland’s sovereignty, administer its affairs abroad, and coordinate political, military, and diplomatic efforts until a legitimate domestic government could be restored.
-
C.
Polish dynasty
A Polish dynasty is a hereditary ruling family originating from Poland that holds political power and influence over the country or its territories across successive generations.
-
D.
Polish person
A Polish person is an individual who identifies with or holds citizenship of Poland, typically sharing its cultural, historical, and linguistic heritage.
-
E.
former territory of Poland
A former territory of Poland is a geographic area that was once under Polish sovereignty or administration but is no longer part of the modern Polish state.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:26 p.m.