Triple
T26585245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianization of Poland |
E667191
|
entity |
| Predicate | baptismOfRuler |
P147141
|
FINISHED |
| Object | Mieszko I of Poland |
—
|
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: Mieszko I of Poland | Statement: [Christianization of Poland, baptismOfRuler, Mieszko I of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baptismOfRuler Context triple: [Christianization of Poland, baptismOfRuler, Mieszko I of Poland]
-
A.
dateOfRoyalBaptism
Indicates the date on which a royal individual underwent their official baptism ceremony.
-
B.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
-
C.
baptismAssociatedWith
chosen
Indicates a relationship in which an entity is connected or related to a baptism event, such as by participation, performance, location, or contextual association.
-
D.
hasEnthronementCeremony
Indicates that an entity formally assumes a position of authority or rulership through an official enthronement ceremony.
-
E.
baptized
Indicates that one entity performed or underwent the religious rite of baptism in relation to another entity or context.
- 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_69f614e47cdc81909786f92cc0d5965f |
completed | May 2, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:05 a.m.