Triple
T26882827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xenia of Saint Petersburg |
E676952
|
entity |
| Predicate | hasTypeOfSanctity |
P67686
|
FINISHED |
| Object | foolishness for Christ |
—
|
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: foolishness for Christ | Statement: [Xenia of Saint Petersburg, hasTypeOfSanctity, foolishness for Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfSanctity Context triple: [Xenia of Saint Petersburg, hasTypeOfSanctity, foolishness for Christ]
-
A.
hasHolinessType
chosen
Indicates a relationship where an entity is assigned or associated with a specific type or category of holiness.
-
B.
hasSanctityComparableTo
Indicates that one entity possesses a level or quality of sanctity that is comparable to that of another entity.
-
C.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
-
D.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
E.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 5:40 a.m.