Triple
T37834238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish presidential election, 1933 |
E943291
|
entity |
| Predicate | underRegime |
P103796
|
FINISHED |
| Object | Sanation regime |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Sanation regime | Statement: [Polish presidential election, 1933, underRegime, Sanation regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underRegime Context triple: [Polish presidential election, 1933, underRegime, Sanation regime]
-
A.
useRegime
Indicates a relationship where a particular method, system, or set of rules is applied or followed in carrying out an action or process.
-
B.
underRule
chosen
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
C.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
-
D.
underPoliticalAuthority
Indicates that one entity is subject to the political control, governance, or jurisdiction of another entity.
-
E.
laterUnderRuleOf
Indicates that one entity came to be governed or ruled by another entity at a later point in time.
- F. None of above.
Provenance (3 batches)
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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:19 p.m.