Triple
T18323708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedoseevtsy |
E438946
|
entity |
| Predicate | typeOfAsceticism |
P76365
|
FINISHED |
| Object | communal and lay asceticism |
—
|
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: communal and lay asceticism | Statement: [Fedoseevtsy, typeOfAsceticism, communal and lay asceticism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAsceticism Context triple: [Fedoseevtsy, typeOfAsceticism, communal and lay asceticism]
-
A.
hasAsceticType
chosen
Indicates that an entity is associated with or characterized by a specific form or type of ascetic practice or lifestyle.
-
B.
viewOnAsceticism
Indicates a stance or opinion someone holds regarding the value, practice, or principles of asceticism.
-
C.
renouncedWorldlyLife
Indicates that an entity has voluntarily given up worldly life, including material pursuits and social obligations, often in favor of a spiritual or ascetic path.
-
D.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
E.
asceticPracticeDuration
Indicates the length of time that an ascetic practice is or was undertaken.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa886508190902ffc26b30731ae |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.