Triple
T14457418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland (seniorate system) |
E358491
|
entity |
| Predicate | actualEffect |
P53074
|
FINISHED |
| Object | political fragmentation of Poland |
—
|
LITERAL FINISHED |
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: political fragmentation of Poland | Statement: [Poland (seniorate system), actualEffect, political fragmentation of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualEffect Context triple: [Poland (seniorate system), actualEffect, political fragmentation of Poland]
-
A.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
-
B.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
C.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
D.
providesEffect
Indicates that one entity causes, delivers, or produces a particular effect or outcome on another entity.
-
E.
predictedEffect
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a9c0d48190ae015e5e0db806ca |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.