Triple
T502525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Slavs |
E10428
|
entity |
| Predicate | conversionToChristianity |
P4040
|
FINISHED |
| Object | 9th century |
—
|
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: 9th century | Statement: [West Slavs, conversionToChristianity, 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionToChristianity Context triple: [West Slavs, conversionToChristianity, 9th century]
-
A.
conversionToChristianityCentury
chosen
Indicates the century during which an entity underwent or was associated with a conversion to Christianity.
-
B.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
C.
religiousReception
Indicates a relationship where one entity formally receives, welcomes, or hosts another in a specifically religious or faith-based context.
-
D.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
E.
formerReligiousAffiliation
Indicates that an entity previously adhered to a particular religion or religious denomination but no longer does so.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1339748819089f89691a1698dd9 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.