Triple
T26585256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianization of Poland |
E667191
|
entity |
| Predicate | effectOnState |
P53074
|
FINISHED |
| Object | international recognition of the Polish state |
—
|
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: international recognition of the Polish state | Statement: [Christianization of Poland, effectOnState, international recognition of the Polish state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnState Context triple: [Christianization of Poland, effectOnState, international recognition of the Polish state]
-
A.
conditionalEffect
Indicates that one event, state, or action occurs or holds only if a specified condition is met.
-
B.
effectOnOutput
Indicates how one factor, action, or condition influences or changes the resulting output of a process or system.
-
C.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
D.
effectOnFlags
Indicates how an action or event changes, sets, or influences the state of one or more flags.
-
E.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 2:05 a.m.