Triple
T26585250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christianization of Poland |
E667191
|
entity |
| Predicate | baptismRite |
P10990
|
FINISHED |
| Object | Latin rite |
—
|
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: Latin rite | Statement: [Christianization of Poland, baptismRite, Latin rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baptismRite Context triple: [Christianization of Poland, baptismRite, Latin rite]
-
A.
baptismAssociatedWith
Indicates a relationship in which an entity is connected or related to a baptism event, such as by participation, performance, location, or contextual association.
-
B.
baptismReligion
Indicates the religion or denomination into which an entity was baptized.
-
C.
baptismEvent
Indicates an event in which a person undergoes the religious rite of baptism, typically involving a ceremonial use of water to mark initiation or purification.
-
D.
practicesBaptismType
chosen
Indicates that an entity performs or follows a specific type or form of baptism as part of its religious practice.
-
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_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 2:05 a.m.