Triple
T17727697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euphrosyne of Polotsk |
E442506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Belarusian saint |
C16266
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Belarusian saint Context triple: [Euphrosyne of Polotsk, instanceOf, Belarusian saint]
-
A.
Hungarian saint
A Hungarian saint is a canonized or beatified individual of Hungarian origin or closely tied to Hungary whose life and deeds are venerated within Christian tradition, particularly in the Catholic and Eastern Christian churches.
-
B.
Orthodox saint
chosen
An Orthodox saint is a person recognized by the Eastern Orthodox Church as having lived a life of exceptional holiness and faithfulness to God, serving as an intercessor and example for believers.
-
C.
Polish Roman Catholic saint
A Polish Roman Catholic saint is a canonized individual from Poland recognized by the Catholic Church for exemplary holiness, virtue, and often martyrdom, serving as a spiritual model and intercessor for the faithful.
-
D.
Georgian Orthodox saint
A Georgian Orthodox saint is a holy person recognized by the Georgian Orthodox Church for their exemplary faith, virtuous life, and often martyrdom, and is venerated as an intercessor and model of Christian living.
-
E.
Armenian saint
An Armenian saint is a holy figure recognized within the Armenian Apostolic or Armenian Catholic traditions for exemplary faith, virtue, and often martyrdom, and venerated as an intercessor and spiritual model for the faithful.
- F. None of above.
Provenance (1 batch)
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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:07 a.m.