Triple
T29903259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | early Polish state |
E759467
|
entity |
| Predicate | christianizationYear |
P35940
|
FINISHED |
| Object | 966 |
—
|
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: 966 | Statement: [early Polish state, christianizationYear, 966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: christianizationYear Context triple: [early Polish state, christianizationYear, 966]
-
A.
dateOfChristianization
chosen
Indicates the date on which a person, group, or place was converted to Christianity or formally adopted the Christian faith.
-
B.
christianizationAssociatedWith
Indicates an association between something and the process or influence of Christianization, such as its promotion, facilitation, or close connection to the spread of Christianity.
-
C.
christianizationRuler
Indicates that a ruler is responsible for or associated with the process of converting people or territories to Christianity.
-
D.
conversionToChristianityCentury
Indicates the century during which an entity underwent or was associated with a conversion to Christianity.
-
E.
ascendedThroneYear
Indicates the year in which a person formally ascended to or took possession of a throne or ruling position.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677311f3881909ccee017947e043b |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:07 p.m.